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: davelentz on Nov 16, '05 08:20:16AM

And just to clarify things, having multiple "versions" of java installed is not a new thing. If you go into Terminal and type:

ls /System/Library/Frameworks/JavaVM.framework/Versions/

You will see that version 1.3.1 still exists, alongside 1.4.2 and 1.5.0.

A "stack" of java versions has been the case in OS X for a long time, the novelty here is that the "current" version does not point to the highest level version.

I suspect this is due to the bulk of the java apps not being ready for 1.5 yet -- at least so far as web usage goes, this would be the case. By sticking with 1.4 as the "default" level of java, we probably achieve the best degree of compatibility with java usage out in the real world.

Developers will, quite naturally, want to reset the "current" link to point to whatever version they wish to work with. It used to be that the way to do this was via setting of symbolic link(s) to point to the desired version of Java. With this 1.5 update, there is a preference utility in /Applications/Utilities/Java/J2SE 5.0/ that specifies which is the default version of java. Oddly enough, this utility only supports setting the nominal version of java to either 1.4.2 or 1.5.0 -- developers wanting to test using 1.3.1 will have to continue to manipulate symbolic links to make 1.3.1 the target.



[ Reply to This | # ]
not changing symbolic links
Authored by: hayne on Nov 16, '05 10:52:23AM
Developers will, quite naturally, want to reset the "current" link to point to whatever version they wish to work with
No - it is not necessary (and undesirable) to change the symbolic links. Please read my forums posting (referred to above) for details on how developers should handle this via changes to their shell environment and to their IDE preferences.

[ Reply to This | # ]
not changing symbolic links
Authored by: adriansutton on Nov 16, '05 01:50:08PM

And in fact, it has *never* been needed nor has it ever been a good idea to change the symlinks.



[ Reply to This | # ]