maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliotte Rusty Harold (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (MNG-5825) Command line fails if jvm.config and MAVEN_OPTS has duplicates
Date Mon, 23 Dec 2019 12:08:00 GMT

     [ https://issues.apache.org/jira/browse/MNG-5825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Elliotte Rusty Harold resolved MNG-5825.
----------------------------------------
    Resolution: Won't Fix

WAI

> 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
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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
(v8.3.4#803005)

Mime
View raw message