This works:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<includes>
<include>**/*TestSuite*</include>
</includes>
<argLine>-server -Xmx256m</argLine>
<useFile>false</useFile>
<jvm>${JAVA_HOME}/bin/java</jvm>
</configuration>
-----Original Message-----
From: Ruel Loehr [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 1:30 PM
To: Maven Users List
Subject: RE: forking surefire VM
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
-----------------------------
512-342-7840 ext 2011
Yahoo: ruelloehr
Skype: ruelloehr
AOL: dokoruel
-----Original Message-----
From: Mike Perham [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 01, 2006 1:28 PM
To: Maven Users List
Subject: forking surefire VM
We are using JAVA_HOME to point to the VM to use to invoke Maven. This
is fully supported by mvn and mvn.bat. But surefire appears to fork the
VM that is in your PATH. So we are seeing instances where one type of
VM is used to start Maven but another is used to run the tests.
Shouldn't the default be to use the same VM? Why isn't surefire using
JAVA_HOME like the shell scripts do?
mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.7.1/347 - Release Date: 5/24/2006
--
Internal Virus Database is out-of-date.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.7.1/347 - Release Date: 5/24/2006
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
