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

Michael Osipov closed MNG-7556.
-------------------------------
    Fix Version/s: 3.9.0
                       (was: 3.9.0-candidate)
       Resolution: Fixed

Fixed with 
[9c6013891504d5eb1d8bad18772a7fe114131d61|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=9c6013891504d5eb1d8bad18772a7fe114131d61]
 and with 
[0f4387543debd77ab649f97014b72feb4046b3c6|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=0f4387543debd77ab649f97014b72feb4046b3c6]
 for {{maven-3.9.x}} branch.

> Clean up notion between user properties and system properties
> -------------------------------------------------------------
>
>                 Key: MNG-7556
>                 URL: https://issues.apache.org/jira/browse/MNG-7556
>             Project: Maven
>          Issue Type: Task
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.9.0, 4.0.0, 4.0.0-alpha-3
>
>
> For a very long time we have documented that the user can set system 
> properties via {{mvn -Dfoo=bar}}, but actually those are user properties 
> which are promoted to system properties and it some cases system properties 
> cannot be modified *after* the JVM has been started. To properly set system 
> properties there are basically two ways:
> * use {{MAVEN_OPTS}} environment variable
> * use {{.mvn/jvm.config}} file
> A third option in the future we could introduce, like other Java tools, a 
> {{-J-Dfoo=bar}} option with the restriction of the the paragraph above.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to