[
http://jira.codehaus.org/browse/SUREFIRE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138175#action_138175
]
Sebastien Peyron commented on SUREFIRE-501:
-------------------------------------------
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.
{quote}
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: ${jvm}
{quote}
> -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
