[
http://jira.codehaus.org/browse/SUREFIRE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Fabulich closed SUREFIRE-111.
---------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.4)
This may have been fixed at some point, but I can't reproduce this problem with
the latest 2.4 trunk. I've checked in an integration test for forkMode=always
in revision 597777.
> argLine with -Xmx option has no effect
> --------------------------------------
>
> Key: SUREFIRE-111
> URL: http://jira.codehaus.org/browse/SUREFIRE-111
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Reporter: Per Olesen
> Attachments: OutOfMemoryError.log
>
>
> In v2.1.3 of surefire plugin, this worked fine:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <configuration>
> <forkMode>pertest</forkMode>
> <argLine>-Xmx1024M</argLine>
> </configuration>
> </plugin>
> </plugins>
> But after doing a "mvn -U" and getting a v2.2 of the plugin, my tests starts
> failing with OutOfMemoryException again. Doing a "mvn -X" shows me, that it
> actually has read the option:
> ....
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-surefire-plugin:2.2:test' -->
> [DEBUG] (f) argLine = -Xmx1024M
> ....
> But maybe it is not applying the argline?
> Forcing it to run with v2.1.3 makes everyting work again.
--
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
