[
https://issues.apache.org/jira/browse/MNG-7206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510858#comment-17510858
]
Hudson commented on MNG-7206:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-7276 #4
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-7276/4/
> 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.0, 4.0.0-alpha-1
>
>
> 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 evaluated 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.20.1#820001)
