Comments on: Helping JAVA to find its way _HOME http://blog.xebia.com/2009/07/08/helping-java-to-find-its-way-_home/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: iwein http://blog.xebia.com/2009/07/08/helping-java-to-find-its-way-_home/#comment-92079 iwein Tue, 14 Jul 2009 06:34:59 +0000 http://blog.xebia.com/?p=2519#comment-92079 Nice to know that if you don't have the /usr/libexec/java_home you probably need to install java for mac osx update 4 or higher. Nice to know that if you don’t have the /usr/libexec/java_home you probably need to install java for mac osx update 4 or higher.

]]> By: Luís Miranda http://blog.xebia.com/2009/07/08/helping-java-to-find-its-way-_home/#comment-92042 Luís Miranda Thu, 09 Jul 2009 11:21:10 +0000 http://blog.xebia.com/?p=2519#comment-92042 Good find! :) Good find! :)

]]> By: Porter http://blog.xebia.com/2009/07/08/helping-java-to-find-its-way-_home/#comment-92038 Porter Wed, 08 Jul 2009 21:09:18 +0000 http://blog.xebia.com/?p=2519#comment-92038 Interesting. I find myself doing something sort of similar on Windows systems on occasion. Essentially, I end up creating 2 - 3 JAVA_"HOME" variables... Where: JAVA_14 -> path to Java 1.4 installation JAVA_15 -> path to Java 1.5 installation JAVA_16 -> path to Java 1.6 installation Then, I just toggle JAVA_HOME = JAVA_14|15|16 as needed. The command path uses JAVA_HOME\bin and so does the classpath variable. Makes it relatively easy to toggle between various Java execution environments for local applications. The tricky bit is dealing with the browser plugin etc. Also on Linux (Ubuntu) it's fairly easy to use 'sudo update-alternatives --config java' and use the menu to select which Java to use... (and you can use the same technique - EXPORT JAVA13, etc. as on Windows.) Interesting.

I find myself doing something sort of similar on Windows systems on occasion. Essentially, I end up creating 2 – 3 JAVA_”HOME” variables… Where:

JAVA_14 -> path to Java 1.4 installation
JAVA_15 -> path to Java 1.5 installation
JAVA_16 -> path to Java 1.6 installation

Then, I just toggle JAVA_HOME = JAVA_14|15|16 as needed. The command path uses JAVA_HOME\bin and so does the classpath variable. Makes it relatively easy to toggle between various Java execution environments for local applications. The tricky bit is dealing with the browser plugin etc.

Also on Linux (Ubuntu) it’s fairly easy to use ‘sudo update-alternatives –config java’ and use the menu to select which Java to use…

(and you can use the same technique – EXPORT JAVA13, etc. as on Windows.)

]]>