You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stuart McCulloch (JIRA)" <ji...@apache.org> on 2017/02/13 10:30:41 UTC
[jira] [Created] (MNG-6172) Precedence of command-line system
property options has changed
Stuart McCulloch created MNG-6172:
-------------------------------------
Summary: Precedence of command-line system property options has changed
Key: MNG-6172
URL: https://issues.apache.org/jira/browse/MNG-6172
Project: Maven
Issue Type: Bug
Components: Command Line
Reporter: Stuart McCulloch
The current state of master (what will eventually become 3.5.0) has reversed the precedence of command-line system property options compared to previous releases of Maven.
For example, running this command with a basic project:
{code}
mvn -Dmaven.repo.local=/tmp/aaa -Dmaven.repo.local=/tmp/zzz validate
{code}
using current master will cause {{/tmp/aaa}} to be created (first-one-wins), whereas for all previous releases of Maven {{/tmp/zzz}} would have been created (last-one-wins)
This has the potential to break CI builds which relied on the previous last-one-wins behaviour.
This was introduced by the fix for MNG-6078 https://github.com/apache/maven/commit/ca4303031357a7decaee8de770b71fb2c2fedd28 - by reversing the whole array the precedence between options on the same command line has been reversed, not just the relationship between .mvn/maven.config options and command line options.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)