[
http://jira.codehaus.org/browse/SUREFIRE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94217
]
Jonas Olsson commented on SUREFIRE-136:
---------------------------------------
A work-around is to edit the mvn-script to insert JAVA_HOME/bin at head of PATH
before execution.
> The plugin does not use JAVA_HOME variable and launches default JVM
> -------------------------------------------------------------------
>
> Key: SUREFIRE-136
> URL: http://jira.codehaus.org/browse/SUREFIRE-136
> Project: Maven Surefire
> Issue Type: Improvement
> Environment: Windows 2000, Maven 2.0.4
> Reporter: Andrey Somov
> Assignee: Carlos Sanchez
> Priority: Minor
> Fix For: 2.4
>
> 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
