maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gisbert Amm (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MPJCOVERAGE-35) MAVEN_OPTS is not being set correctly
Date Fri, 01 Dec 2006 17:27:23 GMT
    [ http://jira.codehaus.org/browse/MPJCOVERAGE-35?page=comments#action_81602 ] 
            
Gisbert Amm commented on MPJCOVERAGE-35:
----------------------------------------

I had a similar problem today.

A possible workaround could be to set *both*, -XX:PermSize=256m and -XX:MaxPermSize=256m (see
http://www.unixville.com/~moazam/stories/2004/05/17/maxpermsizeAndHowItRelatesToTheOverallHeap.html)

> MAVEN_OPTS is not being set correctly
> -------------------------------------
>
>                 Key: MPJCOVERAGE-35
>                 URL: http://jira.codehaus.org/browse/MPJCOVERAGE-35
>             Project: maven-jcoverage-plugin
>          Issue Type: Bug
>         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

        

Mime
View raw message