maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <>
Subject [jira] [Resolved] (MNG-6172) Precedence of command-line system property options has changed
Date Thu, 23 Feb 2017 14:38:44 GMT


Stephen Connolly resolved MNG-6172.
       Resolution: Fixed
    Fix Version/s:     (was: 3.5.0-candidate)

Fixed with dc9c4db4494b62e2231bb67b39678decf6329852 in maven-core

> Precedence of command-line system property options has changed
> --------------------------------------------------------------
>                 Key: MNG-6172
>                 URL:
>             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
> 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
> This was introduced by the fix for MNG-6078
- 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

This message was sent by Atlassian JIRA

View raw message