[jira] [Comment Edited] (MNG-7206) Properly prioritize JVM options from MAVEN_OPTS and jvm.config

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392327#comment-17392327 ] 

Michael Osipov edited comment on MNG-7206 at 8/3/21, 2:16 PM:
--------------------------------------------------------------

Alternatively, we define that {{MAVEN_OPTS}} will override {{jvm.config}} if the JVM accepts an override, e.g., system properties. But this would also mean that if someone defines {{MAVEN_OPTS}} in {{mavenrc}} it will always override project-specific settings.

[~rfscholte], [~hboutemy], WDYT? Which makes more sense for us?


was (Author: michael-o):
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)