[ http://jira.codehaus.org/browse/MSUREFIRE-129?page=comments#action_66921 ]
Per Olesen commented on MSUREFIRE-129: -------------------------------------- Tried it with fork mode "always" which did NOT work. In the debug output I observed: [DEBUG] (f) forkMode = always But it did not fork (I saw no java cmdline). Tried it with "once", which works fine. So am using that now. Can we conclude, that "always" does not work then? BTW: The current online docs say: "Option to specify the forking mode. Can be "never" (default), "once" or "always". "none" and "pertest" are also accepted for backwards compatibility." > argLine with -Xmx option has no effect > -------------------------------------- > > Key: MSUREFIRE-129 > URL: http://jira.codehaus.org/browse/MSUREFIRE-129 > Project: Maven 2.x Surefire Plugin > Type: Bug > Versions: 2.2 > Reporter: Per Olesen > Priority: Minor > 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
