[ http://jira.codehaus.org/browse/MSUREFIRE-65?page=comments#action_60580 ]
Brett Porter commented on MSUREFIRE-65:
---------------------------------------
BTW, to those testing it do either:
a) add this to your POM
<pluginRepositories>
<pluginRepository>
<id>apache.snapshots</id>
<url>http://cvs.apache.org/maven-snapshot-repository</url>
</pluginRepository>
</pluginRepositories>
<repositories>
<repository>
<id>apache.snapshots</id>
<url>http://cvs.apache.org/maven-snapshot-repository</url>
</repository>
</repositories>
(there are reportedly still some problems doing it this way)
OR
b) build it. But make sure you use -Dmaven.test.skip=true the first time
on surefire itself as the old plugin tries to use the new classes which
don't match.
you need to first build the surefire-testng branch, and then the
maven-surefire-plugin-testng branch.
HTH
> Surefire causes OOM
> -------------------
>
> Key: MSUREFIRE-65
> URL: http://jira.codehaus.org/browse/MSUREFIRE-65
> Project: Maven 2.x Surefire Plugin
> Type: Bug
> Versions: 2.1.1
> Reporter: Mike Perham
> Fix For: 2.2
>
>
> We have a build with 30-40 modules which use JUnit to run a heavy load of
> database integration testing. Our build has never worked with just 'mvn
> clean install' since 2.0 - we get OOM errors within 5-10 modules (even with
> -Xmx512m). When I enable the test skip flag, the entire build runs to
> completion. I suspect there is a memory leak somewhere in surefire or its
> classloader where things are not getting freed after each module's test run.
> We are currently using surefire-plugin 2.1.1 since 2.1.2 has MSUREFIRE-59.
--
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
