[MNG-2931] DefaultArtifactCollector changes the version of the originatingArtifact if it's in the dependencyManagement with another version

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0.5, 2.0.6
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Carlos Sanchez Gonzalez
• Created: 04/Apr/07 20:31
• Updated: 30/Dec/09 10:39
• Resolved: 30/Dec/09 10:39

Description

DefaultDependencyTreeBuilder
https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree/src/main/java/org/apache/maven/shared/dependency/tree/DefaultDependencyTreeBuilder.java

calls collect like this

collector.collect( project.getDependencyArtifacts(), project.getArtifact(), managedVersions, repository,
project.getRemoteArtifactRepositories(), metadataSource, null,
Collections.singletonList( listener ) );

Problem:
This pom
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-component-api/1.0-alpha-22/plexus-component-api-1.0-alpha-22.pom
extends
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-containers/1.0-alpha-22/plexus-containers-1.0-alpha-22.pom
that in dependencyManagement has org.codehaus.plexus:plexus-component-api:1.0-alpha-19

so during collect project.getArtifact().getVersion() is changed to the managedVersion instead of the original one

Either this is a bug or an exception should be thrown when originatingArtifact is in managedVersions

Issue Links

• is related to: MNG-2919 Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact