You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Gareth Healy (JIRA)" <ji...@apache.org> on 2015/05/17 14:27:59 UTC

[jira] [Created] (MNG-5825) Command line fails if jvm.config and MAVEN_OPTS has duplicates

Gareth Healy created MNG-5825:
---------------------------------

             Summary: Command line fails if jvm.config and MAVEN_OPTS has duplicates
                 Key: MNG-5825
                 URL: https://issues.apache.org/jira/browse/MNG-5825
             Project: Maven
          Issue Type: Improvement
    Affects Versions: 3.3.3
            Reporter: Gareth Healy
            Priority: Minor


MNG-5790 introduced jvm.config (+1) but how it currently handles MAVEN_OPTS and jvm.config is quite simple, in that it just concats the two values together.

The problem being, if you have:

export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
jvm.config = -Xmx2048m -Xms2048m -XX:MaxPermSize=512m -Djava.awt.headless=true

You get a JAVA issue:

localhost:project garethah$ mvn clean install
Error occurred during initialization of VM
Incompatible minimum and maximum heap sizes specified

Do to the fact that the command line has multiple options for the same JVM option.

Can this be improved, so it takes the higher of the values?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)