You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/08/03 14:13:00 UTC
[jira] [Commented] (MNG-7206) Properly prioritize JVM options from
MAVEN_OPTS and jvm.config
[ https://issues.apache.org/jira/browse/MNG-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392327#comment-17392327 ]
Michael Osipov commented on MNG-7206:
-------------------------------------
Alternatively, we define that {{MAVEN_OPTS}} will override {{jvm.config}} if the JVM accepts an override, e.g., system properties.
[~rfscholte], [~hboutemy], WDYT? Which makes more sense for us?
> Properly prioritize JVM options from MAVEN_OPTS and jvm.config
> --------------------------------------------------------------
>
> Key: MNG-7206
> URL: https://issues.apache.org/jira/browse/MNG-7206
> Project: Maven
> Issue Type: Task
> Components: Command Line
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> We currently have two ways of settings options with the JVM:
> 1. {{MAVEN_OPTS}}
> 2. {{.mvn/jvm.config}}
> We should correctly implement and document priority of those two.
> If we go from general to specific, a generic option shall be overridable (if possible) with a specific one. Thus, first {{MAVEN_OPTS}} is evaluted then {{jvm.config}} since the former applies to all executions while the latter applies to a specific project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)