Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317634 - [launcher] Please do not overwrite exported JAVA_HOME variable
Summary: [launcher] Please do not overwrite exported JAVA_HOME variable
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M2   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 15:41 EDT by Benjamin Drung CLA
Modified: 2010-08-27 15:49 EDT (History)
3 users (show)

See Also:

Attachments
java-home.patch (514 bytes, patch)
2010-06-22 15:41 EDT, Benjamin Drung CLA 		no flags Details | Diff
patch (1.73 KB, patch)
2010-08-27 15:48 EDT, Andrew Niefer CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Drung CLA 2010-06-22 15:41:51 EDT 
Created attachment 172453 [details]
java-home.patch

Please do not overwrite exported JAVA_HOME variable in org.eclipse.equinox.executable (patch attached).
Comment 1 Andrew Niefer CLA 2010-08-27 15:48:30 EDT 
Created attachment 177644 [details]
patch

Would like to use the -java argument if it is passed in instead of a pre-existing JAVA_HOME.

Updated patch uses java in this order of precedence:
1) passed in -java
2) existing JAVA_HOME
3) default java home as specified in the build.sh for some platforms

In all cases, we restore the JAVA_HOME to the original value at the end of the script.
Comment 2 Andrew Niefer CLA 2010-08-27 15:49:43 EDT 
released to head