CODEWITHSUNDEEP
macosjava
Eric
Eric

Reputation: 5402

How to get JDK 1.5 on Mac OS X

I've got to write some code for a legacy application that is still running JDK 1.5. Unfortunately, it looks like OS X doesn't actually have a 1.5 JDK installed; it just links to 1.6:

/System/Library/Frameworks/JavaVM.framework/Versions $ ls -l
lrwxr-xr-x  1 root  wheel    5 Apr 26 11:53 1.3 -> 1.3.1
drwxr-xr-x  3 root  wheel  102 Feb 11 15:33 1.3.1
lrwxr-xr-x  1 root  wheel   10 Apr 26 11:53 1.4 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10 Apr 26 11:53 1.4.2 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10 Apr 26 11:53 1.5 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10 Apr 26 11:53 1.5.0 -> CurrentJDK
lrwxr-xr-x  1 root  wheel    5 Apr 26 11:53 1.6 -> 1.6.0
drwxr-xr-x  7 root  wheel  238 Apr 26 11:53 1.6.0
drwxr-xr-x  8 root  wheel  272 Apr 26 11:53 A
lrwxr-xr-x  1 root  wheel    1 Apr 26 11:53 Current -> A
lrwxr-xr-x  1 root  wheel    3 Apr 26 11:53 CurrentJDK -> 1.6

It sounds like from http://developer.apple.com/java/faq/ that Java is part of the OS update...I'm on Mac OS X v10.6.3 (Snow Leopard). Is there a way to get an actual 1.5 JDK installed on this OS version?

Or do I need to try and find an old version of OS X before I can do this work?

Upvotes: 23

Views: 49065

Answers (8)

oligofren
oligofren

Reputation: 22923

The absolutely easiest way is to use this script by Brice Dutheil. Save the script, download the dmg from Apple (the script will tell you the URI), and run the script. Voila!

Upvotes: 3

James Tikalsky
James Tikalsky

Reputation: 3996

There are really two problems here:

  1. Installing an old version of Java, and keeping Software Update from removing it.
  2. Telling applications that require the older version where to find it, while letting everything else benefit from the latest version.

I don't have anything to add (yet) to what has already been written about installing an old version of Java, however, according to this post from Mike Swingler, Java Runtime Engineer at Apple:

Nobody can or should should be changing symlinks in /System/Library/ Frameworks/JavaVM.framework except for Apple software updates (and we are loath to do so, because it inevitably breaks someone)

In other words, updating the Operating System's links to the old copy of Java is a questionable practice, as it forces every Java application on the system to use the old Java version.

The right way is to set JAVA_HOME to the correct version of Java on an as-needed basis. You can do this by executing /usr/libexec/java_home to get the path to a specific version. For example, to get the path to a 1.5 version:

/usr/libexec/java_home --version 1.5

Upvotes: 8

Rafael Cordones
Rafael Cordones

Reputation: 831

Have a look at http://wiki.oneswarm.org/index.php/OS_X_10.6_Snow_Leopard on how to get and install 1.4 and 1.5 JDKs on Snow Leopard. Also bear in mind that whenever you run Software Update and a JDK update is installed, you will need to "fix" the symlinks to the 1.4 and 1.5 JDKs.

UPDATE: as a side note, for those developing with several JDKs on OS X, have a look at this handy little utility to switch JDK from the command line: setjdk.

Upvotes: 13

n13
n13

Reputation: 6983

Thanks this works great: http://wiki.oneswarm.org/index.php/OS_X_10.6_Snow_Leopard

Strangely, you must follow the renaming steps in the instructions, where you mod the symlinks for 1.5 and 1.5.0 to the actual leopard Java 1.5 - if you don't do that and just try to run the java binary, you get a bus error!

In any case, thanks to these steps I now have an actual Java 5 JDK to compile and run against in Eclipse, which saves me lots of trouble. For one thing, I can find and remove references to Java 1.6-only methods instantly. It's great. Before these would only show up in QA, or even worse, when one of the few customers still on Java 5 tried to run our program. Which was. Bad.

This is why "supporting" JDK5 while actually just pointing symlinks to Java 6 is not good enough for development.

Upvotes: 3

corvi42
corvi42

Reputation: 11

Although the -source and -target flags can be used, they don't always produce code which works on all older JREs. I've definitely had occasions where trying to back-compile to an older spec produced code which worked fine for some users, but wouldn't run on others. To be really sure that everyone using a 1.5 or 1.4 JRE can run your code, you should probably do your production builds with a 1.5 or 1.4 JDK.

I found these instructions very helpful on getting a "real" 1.5 and 1.4 JDK installed under snow leopard: http://codethought.com/blog/?p=233

Upvotes: 0

Steven Schlansker
Steven Schlansker

Reputation: 38526

If you're writing code in Eclipse or potentially some other IDE, you should be able to configure it to target 1.5 compliance.

If you are using javac directly, you could try the -source 1.5 and/or -target 1.5 javac options, which may be sufficient for what you're doing? The 1.6 JDK should be able to produce 1.5-compliant code.

Upvotes: 5

Michael Aaron Safyan
Michael Aaron Safyan

Reputation: 95499

You don't need a copy of Java 1.5 in order to develop for it; Java 1.6 is backwards-compatible with Java 1.5, so anything that would work on 1.5 will work on 1.6. The -source and -target flags may be of use in order to ensure that everything works on 1.5. That said, this article will explain how to get a copy of Java 1.5 on Snow Leopard. Be aware, though, that it could potentially trash/harm your system.

Upvotes: 5

J-16 SDiZ
J-16 SDiZ

Reputation: 26910

You need a older version of OS X for that.

Upvotes: -4

Related Questions