[ http://jira.codehaus.org/browse/MSUREFIRE-156?page=comments#action_79082 ] David J. M. Karlsen commented on MSUREFIRE-156: -----------------------------------------------
It can probably be closed as this already happens: mvn.bat (or .sh) uses JAVA_HOME to run maven. Surefire (at least rev441093 in trunk) the system property java.home to find the executable to fork (when in fork mode). Thus this should point to JAVA_HOME if the variable is declared. > The plugin does not use JAVA_HOME variable and launches default JVM > ------------------------------------------------------------------- > > Key: MSUREFIRE-156 > URL: http://jira.codehaus.org/browse/MSUREFIRE-156 > Project: Maven 2.x Surefire Plugin > Issue Type: Improvement > Environment: Windows 2000, Maven 2.0.4 > Reporter: Andrey Somov > Assigned To: Carlos Sanchez > Priority: Minor > Fix For: 2.3 > > Attachments: MSUREFIREREP-25.log > > > The plugin does not use JAVA_HOME variable and launches default JVM (in this > case default is not defined): > [INFO] Surefire report directory: > D:\tools\workspace\DB2Monster\monster-axis\target\surefire-reports > 'java' is not recognized as an internal or external command, > operable program or batch file. > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > JAVA_HOME does not necessary point to the default JVM. > The plugin shall use the same JVM as Maven. -- 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
