Vassal 3.2.6 and Java 7 update 25

Technical Support & Bugs
41

Tried the new build Joel and it worked great. One thing I noticed is VASSAL 3.2.7 is still loading java 6 not 7. Since Java 6 will die on the vine over the next year, is there a way to force VASSAL to load java 7?

Kevin

42

FWIW I was having the same issues as described. Same updates, same issue with 3.2.6. I downloaded the posted 3.2.7-bug one and now it’s running fine. iMac 27" 10.8.4 with all of Apple’s updates applied as of June 21.

43

Same issue for me on iMAC. What is the fix?

:smiley:

44

The Solution

Update your version of JAVA here: http://support.apple.com/kb/DL1572

If you go into terminal and type java -version ,

  • the bad version is build 20.51-b01-456
  • the good version is build 20.51-b01-457

jf

45

THANKS!!!

46

Yes, 3.2.7-8768 fixes the Mac java problem.

47

Thus spake kankoviak:

Tried the new build Joel and it worked great. One thing I noticed is
VASSAL 3.2.7 is still loading java 6 not 7. Since Java 6 will die on
the vine over the next year, is there a way to force VASSAL to load java
7?

What does “die on the vine” mean? Will Java 6 dissappear from your
machine after some update?

–
J.

48

Hi Joel.

Apple has announced it will no longer support Java 6 after another year or so and is trying to get all OS X 10.7 and 10.8 users to switch to Java 7. They will stop having Apple Java 6 updates within a year as well.

Kevin

49

Thus spake kankoviak:

Hi Joel.

Apple has announced it will no longer support Java 6 after another year
or so and is trying to get all OS X 10.7 and 10.8 users to switch to
Java 7. They will stop having Apple Java 6 updates within a year as
well.

Here’s the problem we face:

  • Apple’s app bundle launcher, JavaApplicationStub, doesn’t work with
    Java 7.

  • AppBundler, which is the semiofficial replacement from Oracle, doesn’t
    work with Java 6.

  • Apple is pushing bundling a JRE with Java apps.

  • Oracle’s Java 7 requires at least OS X 10.7.3.

So: We can’t bundle a Java 7 JRE only because that won’t work for users
with older Macs. We can’t use JavaApplicationStub only for launching,
because that won’t work for users who don’t have Java 6. We can’t use
AppBundler only because that won’t work for users who don’t have Java 7.
I’ve tried building a bundle containing both JavaApplicationStub and
the launcher used by AppBundler, without success. I’d like to avoid
making two Mac bundles. With two bundles, people can get the wrong one,
which means increased support burden for us.

If you have a suggestion for how to handle this, please propose it. I
don’t see any acceptable options right now.

–
J.