[MNG-4913] [regression] User properties override equally named POM properties of transitive dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0.2
• Component/s: Artifacts and Repositories
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 23/Nov/10 17:10
• Updated: 20/Feb/11 07:15
• Resolved: 23/Nov/10 18:12

Description

While trying to run the core ITs using -DmavenVersion=3.0.1 the build ended up with a resolution failures for a bunch of non-existing artifacts like maven-reporting-api:3.0.1. The problematic artifact versions were coming from a wrong dependency tree like this:

DEBUG] org.apache.maven.plugins:maven-resources-plugin:jar:2.3:
DEBUG]    org.apache.maven:maven-plugin-api:jar:2.0.6:compile
DEBUG]    org.apache.maven:maven-project:jar:2.0.6:compile
DEBUG]       org.apache.maven:maven-settings:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-profile:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-model:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-artifact-manager:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-plugin-registry:jar:3.0.1:compile
DEBUG]       org.apache.maven:maven-artifact:jar:3.0.1:compile

Note that the dependencies of maven-project:2.0.6 use the wrong version.

The problem is due to maven:pom:2.0.6 using the POM property mavenVersion which erroneously gets overridden by my user property.

During dependency resolution, user properties must be treated like system properties and must not override POM properties.

Issue Links

• relates to: MNG-5018 Do not allow properties in current reactor to change dependencies of artifacts from repositories