[#SUREFIRE-501] -Xmx JVM option is not used by the surefire process - jira.codehaus.org

Maven Surefire

-Xmx JVM option is not used by the surefire process

Created: 11/Jun/08 08:01 AM Updated: 03/Nov/09 03:41 AM

Component/s:

process forking

Affects Version/s:

2.4.2

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Windows XP SP2, JDK 1.6, Maven 2.0.9, surefire 2.4.2

Complexity:

Intermediate

Description

« Hide

I use the jvm option "-Xmx1024m" to execute maven 2.0.9. I've got heavy integration tests.
When the process surefire forks, it does not use this option. His maximum heap size is only 65 MB.

Sort Order:

[ Permalink | « Hide ]

Olivier Lamy added a comment - 11/Jun/08 08:06 AM

have a look at argLine configuration (http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#argLine)

[ Permalink | « Hide ]

Sebastien Peyron added a comment - 11/Jun/08 08:31 AM

Thanks you, but I don't know how to use it.

I am still thinking it's a strange.
The following lines are extracted from the documentation.

jvm Option to specify the jvm (or path to the java executable) to use with the forking options. For the default, the jvm will be the same as the one used to run Maven.
Type: java.lang.String
Since: 2.1
Required: No
Expression: $
Unknown macro: {jvm}

[ Permalink | « Hide ]

Benjamin Bentmann added a comment - 11/Jun/08 08:39 AM

but I don't know how to use it.

<configuration>
  <argLine>-Xmx1024m</argLine>
</configuration>

should do.

For the default, the jvm will be the same as the one used to run Maven.

In this context, "jvm" refers merely to the executable used to launch the JVM, this does not include the options for the JVM.

[ Permalink | « Hide ]

Brett Porter added a comment - 03/Nov/09 03:41 AM

so, should the surefire plugin also inherit the Maven options? I think there's value in having a separate environment instead.