[ http://jira.codehaus.org/browse/MNG-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Stiepel updated MNG-5025: -------------------------------- Attachment: mvn.bat the changed mvn.bat > CLONE - JAVA_HOME auto discovery - also for windows with mvn.bat > ---------------------------------------------------------------- > > Key: MNG-5025 > URL: http://jira.codehaus.org/browse/MNG-5025 > Project: Maven 2 & 3 > Issue Type: Improvement > Affects Versions: 3.0.2 > Environment: Linux, Ubuntu > Reporter: Jochen Stiepel > Priority: Minor > Attachments: mvn.bat > > > 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 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira