when fork is enabled, Surefire should use the same JVM running Maven (i.e. use
java.home sysprop), rather than expecting java to be in the system PATH
------------------------------------------------------------------------------------------------------------------------------------------------------
Key: MSUREFIRE-127
URL: http://jira.codehaus.org/browse/MSUREFIRE-127
Project: Maven 2.x Surefire Plugin
Type: Improvement
Versions: 2.2
Reporter: Ian Springer
Here's the thread from maven-users:
+1
(Haven't been bitten by this yet, but it is certainly not intuitive.)
On 6/1/06, Mike Perham <[EMAIL PROTECTED]> wrote:
> +1
>
> -----Original Message-----
> From: Ian Springer [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 01, 2006 2:36 PM
> To: Maven Users List
> Subject: RE: forking surefire VM
>
> I think the default should be the same JVM that launched Maven (i.e.
> System.getProperty("java.home") + File.pathSeparator + "bin" +
> File.pathSeparator + "java"). This seems more intuitive.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Carlos Sanchez
> Sent: Thursday, June 01, 2006 3:20 PM
> To: Maven Users List
> Subject: Re: forking surefire VM
>
> http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html
>
> jvm: Option to specify the jvm (or path to the java executable) to use
> with the forking options. For the default we will assume that java is
> in the path.
>
>
> On 6/1/06, Ruel Loehr <[EMAIL PROTECTED]> wrote:
> > I've seen this as well. There is an option for setting which vm to
> use, I had to use it work around the problem. Maybe you could open a
> jira issue for it.
> >
> > Ruel Loehr
> > JBoss QA
--
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
