Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: About the Java SE 5.0 Release 3 update' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: About the Java SE 5.0 Release 3 update
Authored by: adriansutton on Nov 16, '05 01:48:43PM

You *never* need to modify the /System folder for Java. To get Eclipse to use Java 1.5, edit it's Info.plist inside the application bundle. The eclipse developers on the Apple java-dev list have outlined this process a number of times.

Better yet, don't run Eclipse on Java 1.5, it provides you with no advantages and it's generally more stable on Java 1.4 - which is why it specifically requests Java 1.4. You can still develop your applications within Eclipse using Java 1.5 and run your applications from within Eclipse under Java 1.5 by using Eclipse's preferences.

Do not modify the /System directory, it will cause you trouble when upgrading.



[ Reply to This | # ]
10.4: About the Java SE 5.0 Release 3 update
Authored by: raider on Nov 29, '05 10:14:54AM

Eclipse is not the only Java application you know. There are lots of Java applications that do not honor OSXs method of chosing the JVM.

And you say that there is no advantage of using Eclipse under Java 1.5? Well, except faster startup times, and lower memory consumption. But hey - who needs those, right?

You say Eclipse is unstable under Java 1.5? Hmmm. Not a single problem for me yet. But I only use it every day all day long, so I might not have hit anything yet....

You say that changing things in the /System path will screw up updates? Like what? Can you be specific? Because as far as I have seen, since OSX 10.0.4 there have been lots of things that you are able to change under the /System path... Sure - you *can* cause problems, but this change with regards to Java will not cause problems. There are all sorts of things under /System that power users will work with. Preference Panes. Modem Scripts. Startup Items. Fonts. etc etc etc. Java is another one...

What is the hangup? The whole reason the thing USES A SYMLINK in the FIRST PLACE is to allow it to be changed.... That is the whole point.

You keep spouting doom and gloom - while those of us who use it every day have yet to run into any problems. Not that there will never be - but I have read the forums linked to, and I have played around with all the .plist files and whatnot - and the easiest, most consistant, and most effective way is to modify the Symlink. Period. Nothing else guarantees I will use Java 1.5 with all my applications.

So to people reading this - there are clearly two prevailing thoughts on this matter. I have not had a single problem changing the Symlink since the first betas of Java 1.5 came out. I did however have problems getting all sorts of applications to use Java 1.5 until I did change the Symlink.



[ Reply to This | # ]