You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ian Springer (JIRA)" <ji...@codehaus.org> on 2006/06/02 01:12:43 UTC
[jira] Created: (MSUREFIRE-127) 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
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 <Mi...@webifysolutions.com> wrote:
> +1
>
> -----Original Message-----
> From: Ian Springer [mailto:ian.springer@jboss.com]
> 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: carlossg@gmail.com [mailto:carlossg@gmail.com] 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 <ru...@jboss.com> 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
[jira] Moved: (SUREFIRE-135) 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
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SUREFIRE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MSUREFIRE-127 to SUREFIRE-135:
-------------------------------------------------
Affects Version/s: (was: 2.0 (2.2 plugin))
2.0 (2.2 plugin)
Fix Version/s: (was: 2.3)
2.3
Key: SUREFIRE-135 (was: MSUREFIRE-127)
Project: Maven Surefire (was: Maven 2.x Surefire Plugin)
> 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: SUREFIRE-135
> URL: http://jira.codehaus.org/browse/SUREFIRE-135
> Project: Maven Surefire
> Issue Type: Improvement
> Affects Versions: 2.0 (2.2 plugin)
> Reporter: Ian Springer
> Assigned To: Fabrice BELLINGARD
> Fix For: 2.3
>
>
> 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 <Mi...@webifysolutions.com> wrote:
> > +1
> >
> > -----Original Message-----
> > From: Ian Springer [mailto:ian.springer@jboss.com]
> > 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: carlossg@gmail.com [mailto:carlossg@gmail.com] 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 <ru...@jboss.com> 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
[jira] Closed: (MSUREFIRE-127) 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
Posted by "Fabrice BELLINGARD (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSUREFIRE-127?page=all ]
Fabrice BELLINGARD closed MSUREFIRE-127.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.3
> 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
> Issue Type: Improvement
> Affects Versions: 2.2
> Reporter: Ian Springer
> Assigned To: Fabrice BELLINGARD
> Fix For: 2.3
>
>
> 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 <Mi...@webifysolutions.com> wrote:
> > +1
> >
> > -----Original Message-----
> > From: Ian Springer [mailto:ian.springer@jboss.com]
> > 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: carlossg@gmail.com [mailto:carlossg@gmail.com] 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 <ru...@jboss.com> 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