[ http://jira.codehaus.org/browse/MSUREFIRE-129?page=comments#action_73515
]
Hendrik Schreiber commented on MSUREFIRE-129:
---------------------------------------------
I believe I have a similar problem. Specifying disable assertions in 2.2 is
broken, but works fine with 2.1.3.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<!--<version>2.1.3</version> -->
<configuration>
<argLine>-disableassertions</argLine>
</configuration>
</plugin>
leads to:
[....]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-surefire-plugin:2.2:test' -->
[DEBUG] (f) argLine = -disableassertions
[DEBUG] (f) basedir = C:\IdeaProjects\beatunes\trunk\beatunes
[DEBUG] (f) childDelegation = false
[DEBUG] (f) classesDirectory =
C:\IdeaProjects\beatunes\trunk\beatunes\target\classes
[DEBUG] (f) classpathElements = [.....]
[DEBUG] (f) disableXmlReport = false
[DEBUG] (f) forkMode = once
[DEBUG] (f) jvm = java
[DEBUG] (f) localRepository = [local] -> file://C:\Documents and
Settings\Administrator\.m2\repository
[DEBUG] (f) parallel = false
[DEBUG] (f) pluginArtifactMap = [....]
[DEBUG] (f) printSummary = true
[DEBUG] (f) projectArtifactMap = [....]
[DEBUG] (f) remoteRepositories = [[central] -> http://repo1.maven.org/maven2]
[DEBUG] (f) reportFormat = brief
[DEBUG] (f) reportsDirectory =
C:\IdeaProjects\beatunes\trunk\beatunes\target\surefire-reports
[DEBUG] (f) testClassesDirectory =
C:\IdeaProjects\beatunes\trunk\beatunes\target\test-classes
[DEBUG] (f) testSourceDirectory =
C:\IdeaProjects\beatunes\trunk\beatunes\src\test\java
[DEBUG] (f) threadCount = 5
[DEBUG] (f) trimStackTrace = true
[DEBUG] (f) useFile = true
[DEBUG] -- end configuration --
[...]
Forking command line: java -disableassertions -classpath "C:\Documents and Setti
ngs\Administrator\.m2\repository\org\apache\maven\surefire\surefire-api\2.0\sure
fire-api-2.0.jar;C:\Documents and Settings\Administrator\.m2\repository\org\code
haus\plexus\plexus-utils\1.1\plexus-utils-1.1.jar;C:\Documents and Settings\Admi
nistrator\.m2\repository\org\apache\maven\surefire\surefire-booter\2.0\surefire-
booter-2.0.jar" org.apache.maven.surefire.booter.SurefireBooter C:\DOCUME~1\ADMI
NI~1\LOCALS~1\Temp\surefire34197tmp C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefire3
4198tmp
So the commandline argument makes it into the displayed commandline. I just
doubt that that commandline is actually executed.
> argLine with -Xmx option has no effect
> --------------------------------------
>
> Key: MSUREFIRE-129
> URL: http://jira.codehaus.org/browse/MSUREFIRE-129
> Project: Maven 2.x Surefire Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Per Olesen
> Fix For: 2.3
>
> 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
