[bkocik]

I ran an update on my PowerBook the other day that installed some security updates to OS X, upgraded Safari, etc. I don’t know if there’s a relationship or if it’s just a coincidence, but the same day MyEclipse started crashing after startup. It would come up and sit on the desktop for a minute or two, and then crash.

I figured out that when it starts up, it’s using the 1.4.2 JVM/JDK by calling /usr/bin/java. I don’t know for sure if it was doing this before the recent OS update or not; I imagine it was. All of my code is 1.5.x, and I have MyEclipse set up to use that environment and compiler. After I backed up /usr/bin/java and symlinked it to the 1.5.0 version, the crashes seem to have gone away (I’ve had it running now for about a half hour, which is much longer than it was lasting before).

Is there a better way to get it to start up using the JVM of my choice than symlinking /usr/bin/java? I have other apps that may require /usr/bin/java to be 1.4.x.

Thanks . . .

[Riyad Kalla]

Bill,
You can force Eclipse to use your VM by choice by way of the -vm switch:
/usr/bin/eclipse -vm /usr/bin/java

Where you want to point directly at the java executable.

[Author]

Posts