Nik Goile wrote: > Hi Martin, > I'm using Windows XP, Service Pack 2. > > I've got a whole bunch of Java versions installed, including 1.4, 5 and > 6 (does that make sense?).
Sure. Im just working through this now to see how eclipse chooses its VM at startup, so for anyone else having a similar problem, this info might help :) It seems to me that when you went from 'not working' to 'working' the JVM that eclipse uses changed from 1.4 to a newer version. If you go to Help -> About -> Configuration Details you should see a line like this : -vm C:\Program Files\Java\jre1.6.0_02\bin\client\jvm.dll Apparently in eclipse 3.3 this is how the VM gets selected : http://wiki.eclipse.org/Equinox_Launcher#Finding_a_VM.2C_Using_JNI_Invocation_or_Executing_Java ---- When no -vm is specified, the launcher looks for a virtual machine first in a jre directory in the root of eclipse and then on the search path. If java is found in either location, then we look for a jvm shared library (jvm.dll on window, libjvm.so on *nix platforms) relative to that java executable. ---- What exactly constitutes the 'search path' im not sure, but im guessing that on windows it involves some kind of lookup for the latest JVM install. It definitely doesnt require anything in the system path. So, if anyone is still having problems like Nik then let me know which VM eclipse is using and what platform you are running on and we'll see what we can do to get it fixed. > Ps: Now I've got it going, I'm loving the new version of ASDT - > definitely seen a big performance improvement. great. We still have a long way to go but I think we're reaching a nice 'comfort zone' :) martin _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
