[MNG-5020] JAVA_HOME auto discovery

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.2
• Fix Version/s: 3.0.3
• Environment: Linux, Ubuntu
• Assignee: Benjamin Bentmann
• Reporter: Maciej Mazur
• Created: 21/Feb/11 17:20
• Updated: 03/Mar/11 17:17
• Resolved: 24/Feb/11 13:48

Description

When JAVA_HOME is not set (but java command is in the PATH) then bin/mvn script prints warning message "Warning: JAVA_HOME environment variable is not set."
I don't want to explicitly set JAVA_HOME variable because I manage my JDK instances by update-java-alternatives in Ubuntu. It switches system wide JDK, but does not set the JAVA_HOME variable. If I would set JAVA_HOME manually then any changes made by update-java-alternatives would not be reflected in JAVA_HOME which is obviously incorrect.

However mvn script can be improved, so that it can guess JAVA_HOME. Actually Groovy startup script does it very well, so I moved auto-discovery code from groovy script to mvn and attach patch here

Issue Links

• relates to: MNG-5025 CLONE - JAVA_HOME auto discovery - also for windows with mvn.cmd