# VASSAL Bug ID: 2968414 **URL:** \ **Category:** Development\ **Created:** [March 13, 2010, 4:45am UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857 "2010-03-13T04:45:11Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jimcot](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@jimcot](https://forum.vassalengine.org/u/jimcot)\ **Post date:** [March 13, 2010, 4:45am UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/1 "2010-03-13T04:45:11Z")
Guys, I ran across this bug while trying to change a label. It turns out to be a well-known, nasty Java bug. There is a work around that looks pretty painful and we’d have to use the workaround in a lot of places potentially. Is it worth it? ---
**Author:** ![jimcot](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@jimcot](https://forum.vassalengine.org/u/jimcot)\ **Post date:** [March 13, 2010, 4:59am UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/2 "2010-03-13T04:59:31Z")
Ok, I dug deeper and found this is a dupe of 2817004 and is fixed in java version 1.6 update 18. I think it might be worth some sort of popup when VASSAL starts urging folks to upgrade to that version of java if they’re not already there. It’s pretty easy to hit the problem if you use labels. ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [March 13, 2010, 12:02pm UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/3 "2010-03-13T12:02:32Z")
Thus spake “jimcot”: > [@](#): > > Ok, I dug deeper and found this is a dupe of 2817004 and is fixed in java ver > sion 1.6 update 18. I think it might be worth some sort of popup when VASSAL > starts urging folks to upgrade to that version of java if they’re not alread > y there. It’s pretty easy to hit the problem if you use labels. For Mac users who have Java 1.6, the newest version of is Update 17, which has the bug; there’s nothing we can do other than wait for Apple. I’ve never seen this bug reported by a Linux user. My guess is that OpenJDK fixed it a long time ago. The simplest thing to do for Windows users is to bump the minimum Java version for which the installer doesn’t prompt you to update Java. Presently, it’s 1.5.0\_08. I’ll change that to 1.6.0\_18 for 3.1.15. – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [March 13, 2010, 12:22pm UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/4 "2010-03-13T12:22:55Z")
Thus spake Joel Uckelman: > [@](#): > > Thus spake “jimcot”: > > > [@](#): > > > > Ok, I dug deeper and found this is a dupe of 2817004 and is fixed in java v > > er > > > [@](#): > > > > sion 1.6 update 18. I think it might be worth some sort of popup when VASS > > AL > > > [@](#): > > > > starts urging folks to upgrade to that version of java if they’re not alre > > ad > > > [@](#): > > > > y there. It’s pretty easy to hit the problem if you use labels. > > For Mac users who have Java 1.6, the newest version of is Update 17, > which has the bug; there’s nothing we can do other than wait for > Apple. > > I’ve never seen this bug reported by a Linux user. My guess is that > OpenJDK fixed it a long time ago. > > The simplest thing to do for Windows users is to bump the minimum > Java version for which the installer doesn’t prompt you to update Java. > Presently, it’s 1.5.0\_08. I’ll change that to 1.6.0\_18 for 3.1.15. Done in 3.1@6610. – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com)) ---
**Author:** ![wlk](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/wlk/32/101_2.png) [@wlk](https://forum.vassalengine.org/u/wlk)\ **Post date:** [March 14, 2010, 11:39am UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/5 "2010-03-14T11:39:18Z")
BTW, what is the lowest supported java engine (depencies to use when compiling the classes) ? ---
**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\ **Post date:** [March 14, 2010, 11:45am UTC](https://forum.vassalengine.org/t/vassal-bug-id-2968414/2857/6 "2010-03-14T11:45:52Z")
Thus spake “wlk”: > [@](#): > > BTW, what is the lowest supported java engine (depencies to use when compili > ng the classes) ? Presently, we compile releases to be 1.5-compatible (using the ‘-source 5 -target 5’ flags). In practice, the only people who are using Java 5 have older Macs where there is no Java 6 JRE. One unintended side-effect of the check for new versions that VASSAL 3.1 does is that we can use my webserver logs to get an estimate of how many users have older Macs, which will one day help us decide when to move from Java 5 to Java 6. – J. * * * Messages mailing list [Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org) [forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org) Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))