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

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 <Mike.Perham@webifysolutions.com> wrote:
> +1
>
> ----Original Message----
> From: Ian Springer 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 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 <ruel.loehr@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