[ http://jira.codehaus.org/browse/MAVEN-1728?page=comments#action_52431 ]
Tigran Antonyan commented on MAVEN-1728:
----------------------------------------
Thank you for you comments on plugin properties, this did help in a way that
JVM memeory usage is not as high as without forking,
However I'm still having a problem with jcoverage (even if I run it all by
itself as maven maven-jcoverage-plugin:report ), still getting the same error :
jcoverage:on:
instrumenting the class-files...
[instrument] jcoverage 1.0.5 copyright (c)2003 jcoverage ltd.
http://jcoverage.com/
[instrument] jcoverage is licensed under the GNU General Public License
[instrument] jcoverage comes with ABSOLUTELY NO WARRANTY
[instrument] instrumenting 16 classes to
C:\project\javasrc\media\target\jcoverage\classes
java:jar-resources:
test:prepare-filesystem:
test:test-resources:
test:compile:
test:test:
[junit] Running media.client.ClientCommandTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Exception in thread "Thread-2" java.lang.StackOverflowError
[junit] at
com.jcoverage.coverage.InstrumentationFactory.newInstrumentation(InstrumentationFactory.java:88)
[junit] at
com.ge.security.media.server.webservices.GenesisAppender.append(GenesisAppender.java:65)
[junit] at
org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
[junit] at
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
[junit] at org.apache.log4j.Category.callAppenders(Category.java:187)
[junit] at org.apache.log4j.Category.forcedLog(Category.java:372)
[junit] at org.apache.log4j.Category.debug(Category.java:241)
[junit] at
com.jcoverage.coverage.InstrumentationFactory.newInstrumentation(InstrumentationFactory.java:89)
[junit] at
com.ge.security.media.server.webservices.GenesisAppender.append(GenesisAppender.java:65)
------------------------------------
-------------- about 300 lines of simular log for each test class -------------
---------------------------------------
This may be jcoverage issue as well... since the JVM memory usage is much less
now ( about 40m )
> MAVEN_OPTS is not being set correctly
> -------------------------------------
>
> Key: MAVEN-1728
> URL: http://jira.codehaus.org/browse/MAVEN-1728
> Project: Maven
> Type: Bug
> Versions: 1.1-beta-2
> Environment: windows xp
> Reporter: Tigran Antonyan
> Priority: Blocker
>
>
> I set the MAVEN_OPTS to -Xmx1024m (tried from command line and
> %MAVEN_HOME%/bin/maven) and it still fail the build when JVM memory use gets
> up to 220m with either outOfMemory or java heap size exception
> here is a part of the output:
> Root cause
> java.lang.OutOfMemoryError: PermGen space
> Thanks Tigran
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
