You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2008/06/11 15:08:12 UTC
[jira] Commented: (SUREFIRE-501) -Xmx JVM option is not used by the
surefire process
[ http://jira.codehaus.org/browse/SUREFIRE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138169#action_138169 ]
Olivier Lamy commented on SUREFIRE-501:
---------------------------------------
have a look at argLine configuration (http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#argLine)
> -Xmx JVM option is not used by the surefire process
> ---------------------------------------------------
>
> Key: SUREFIRE-501
> URL: http://jira.codehaus.org/browse/SUREFIRE-501
> Project: Maven Surefire
> Issue Type: Bug
> Components: process forking
> Affects Versions: 2.4.2
> Environment: Windows XP SP2, JDK 1.6, Maven 2.0.9, surefire 2.4.2
> Reporter: Sebastien Peyron
>
> 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.
--
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