[jira] [Closed] (MNG-6079) 3.4 regression: cannot override version of a dependencyManagement in a submodule any more
[ https://issues.apache.org/jira/browse/MNG-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6079. -- Resolution: Not A Problem Fix Version/s: (was: 3.6.0-candidate) > 3.4 regression: cannot override version of a dependencyManagement in a > submodule any more > - > > Key: MNG-6079 > URL: https://issues.apache.org/jira/browse/MNG-6079 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: needing-scrub-3.4.0-fallout >Reporter: Samuel Langlois > Attachments: parent-pom.xml, pom.xml > > > When you import a {{}} section from another pom, you > can use a property for the version: > {code} > > > > org.apache.maven.surefire > surefire > ${surefire.version} > pom > import > > > > {code} > In Maven 3.3 and before, that version could be overridden in submodules, by > overriding the property. > In Maven 3.4, this doesn't work any more: redefining the property doesn't > change the dependencies which are defined. > I attach a simple example that uses surefire dependencies. > {{mvn dependency:list}} will yield different results: > * surefire-api:jar:2.12 with Maven 3.3, because this is the overridden > version in the pom > * surefire-api:jar:2.10 with Maven 3.4 (as of snapshot 2016-08-06), which is > the version defined in the parent pom > It is admittedly a corner case, or potentially a bug fix. In Maven 3.4, the > behaviour of is now more consistent with the one of > , where you can't redefine a dependency version simply by > overriding a property. > It is however a change in behaviour -- which broke my build. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MNG-6079) 3.4 regression: cannot override version of a dependencyManagement in a submodule any more
[ https://issues.apache.org/jira/browse/MNG-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6079. -- Resolution: Fixed Fix Version/s: 3.4.0 > 3.4 regression: cannot override version of a dependencyManagement in a > submodule any more > - > > Key: MNG-6079 > URL: https://issues.apache.org/jira/browse/MNG-6079 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.4.0 >Reporter: Samuel Langlois >Assignee: Christian Schulte > Fix For: 3.4.0 > > Attachments: parent-pom.xml, pom.xml > > > When you import a {{}} section from another pom, you > can use a property for the version: > {code} > > > > org.apache.maven.surefire > surefire > ${surefire.version} > pom > import > > > > {code} > In Maven 3.3 and before, that version could be overridden in submodules, by > overriding the property. > In Maven 3.4, this doesn't work any more: redefining the property doesn't > change the dependencies which are defined. > I attach a simple example that uses surefire dependencies. > {{mvn dependency:list}} will yield different results: > * surefire-api:jar:2.12 with Maven 3.3, because this is the overridden > version in the pom > * surefire-api:jar:2.10 with Maven 3.4 (as of snapshot 2016-08-06), which is > the version defined in the parent pom > It is admittedly a corner case, or potentially a bug fix. In Maven 3.4, the > behaviour of is now more consistent with the one of > , where you can't redefine a dependency version simply by > overriding a property. > It is however a change in behaviour -- which broke my build. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6079) 3.4 regression: cannot override version of a dependencyManagement in a submodule any more
[ https://issues.apache.org/jira/browse/MNG-6079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MNG-6079. -- Resolution: Won't Fix Assignee: Christian Schulte Please read MNG-5971 regarding the change to the {{import}} scope and why that change is thought of being a bugfix. > 3.4 regression: cannot override version of a dependencyManagement in a > submodule any more > - > > Key: MNG-6079 > URL: https://issues.apache.org/jira/browse/MNG-6079 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.4.0 >Reporter: Samuel Langlois >Assignee: Christian Schulte > Attachments: parent-pom.xml, pom.xml > > > When you import a {{}} section from another pom, you > can use a property for the version: > {code} > > > > org.apache.maven.surefire > surefire > ${surefire.version} > pom > import > > > > {code} > In Maven 3.3 and before, that version could be overridden in submodules, by > overriding the property. > In Maven 3.4, this doesn't work any more: redefining the property doesn't > change the dependencies which are defined. > I attach a simple example that uses surefire dependencies. > {{mvn dependency:list}} will yield different results: > * surefire-api:jar:2.12 with Maven 3.3, because this is the overridden > version in the pom > * surefire-api:jar:2.10 with Maven 3.4 (as of snapshot 2016-08-06), which is > the version defined in the parent pom > It is admittedly a corner case, or potentially a bug fix. In Maven 3.4, the > behaviour of is now more consistent with the one of > , where you can't redefine a dependency version simply by > overriding a property. > It is however a change in behaviour -- which broke my build. -- This message was sent by Atlassian JIRA (v6.3.4#6332)