harpua:~ mgouker$ ls -l /Library/Java/JavaVirtualMachines
total 0
drwxrwxr-x 3 root wheel 102 Apr 20 2012 1.7.0.jdk
harpua:~ mgouker$ ls -l /System/Library/Frameworks/JavaVM.framework/Versions
total 64
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.4 → CurrentJDK
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.4.2 → CurrentJDK
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.5 → CurrentJDK
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.5.0 → CurrentJDK
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.6 → CurrentJDK
lrwxr-xr-x 1 root wheel 10 Feb 16 08:43 1.6.0 → CurrentJDK
drwxr-xr-x 9 root wheel 306 Feb 16 19:34 A
lrwxr-xr-x 1 root wheel 1 Feb 16 08:43 Current → A
lrwxr-xr-x 1 root wheel 52 Feb 16 09:50 CurrentJDK → /Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents
I also have:
harpua:~ mgouker$ ls /System/Library/Java/JavaVirtualMachines
1.6.0.jdk
Guillaume, if you use 1.7 JDK, please make sure you have Java (not javascript) off in your browser. There are security issues.
Guillaume, our jdks are a little different (you are 13 builds ahead of me). Where did you get yours? From Oracle or the Open JDK project?
I have no problem starting Vassal - absolutely no error executing Vassal, however I still have bad graphic output. I execute Vassal from the Applications folder (not through a browser - can you still do that?).
Also, uekelman, I believe I have the same output on the screen as Guillaume in Vassal itself (i.e. no text on the counters). Please see attached image. Note that the Ottomans are on the rampage.
Guillaume, Vassal will use the Java it finds in its class path. That’s why the links are important. A symbolic link points to the current VM. In your case, it will find jdk 7’s libraries now. Do you just execute the Vassal App in the Applications folder?
That’s correct. The Clash of Monarchs module, like 99% of them, uses JPG/PNG images for all its art assets. My modules use SVG images, and the problem being worked around relates to the rendering of SVG.
[quote=“gdaudin”]
I have a mouse pointer issue when launching vassal in this way.
BTW, Michael, what is the version of Java run by Vassal when you start it “normally” ?
/quote]
The short answer: The first one java finds in your class path.
What we are doing is overriding the existing class path to guarantee that we find only the jars that we know are correct. Your comment before about the system not starting because of the version indicated to me that there was still an invalid connection to a jar from a preexisting version (it was compiled with an earlier library). So uekelman’s technique excluded all the other virtual machines and launching from the command line specifying only the minimal number of jars ruled everything else out.
I will take a look at the mouse cursor a little later. I am so happy to have slept!
Got that. I meant in your install. I assume you have cleaner Java installation than me, and I was wondering how come Vassal does not run in the same way when you start “normally” and by the command line method on your machine.
Or maybe I am utterly confused, which is very plausible.