[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Affects Version/s: (was: 3.5.0-candidate)
> 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
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> 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)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Fix Version/s: (was: 3.5.0-alpha-2)
> 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
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0, 3.5.0-alpha-1
>
>
> 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)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Fix Version/s: 3.5.0-alpha-2
3.5.0-alpha-1
> 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
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Assignee: Stephen Connolly
>Priority: Blocker
> Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> 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)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Fix Version/s: 3.5.0-candidate
> 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
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
> Fix For: 3.5.0-candidate
>
>
> 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)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Affects Version/s: 3.5.0-candidate
> 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
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Priority: Blocker
> Fix For: 3.5.0-candidate
>
>
> 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)
[jira] [Updated] (MNG-6172) Precedence of command-line system property options has changed
[
https://issues.apache.org/jira/browse/MNG-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly updated MNG-6172:
--
Priority: Blocker (was: Major)
> 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
>Affects Versions: 3.5.0-candidate
>Reporter: Stuart McCulloch
>Priority: Blocker
> Fix For: 3.5.0-candidate
>
>
> 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)
