VASSAL Bug ID: 2968414

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?

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.

Thus spake “jimcot”:

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
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake Joel Uckelman:

Done in 3.1@6610.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

BTW, what is the lowest supported java engine (depencies to use when compiling the classes) ?

Thus spake “wlk”:

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
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)