[
http://jira.codehaus.org/browse/MNG-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=142027#action_142027
]
John Casey commented on MNG-3667:
---------------------------------
This is a quirk of a bad POM:
http://repo1.maven.org/maven2/org/apache/ws/commons/XmlSchema/1.1/XmlSchema-1.1.pom
Take a look at the version string inside that POM.
I'm adjusting the MavenMetadataSource to take groupId/artifactId/version from
the (potentially relocated) artifact instead of the (potentially relocated)
project instance, which should clear this up for consumers of this bad metadata.
> Dependencies resolution is wrong in some cases (xfire-core:1.2.6 for example)
> -----------------------------------------------------------------------------
>
> Key: MNG-3667
> URL: http://jira.codehaus.org/browse/MNG-3667
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.10
> Environment: 2.0.10-RC1
> Reporter: Arnaud Heritier
> Priority: Blocker
> Fix For: 2.0.10
>
> Attachments: xfire-maven-2.0.10.zip
>
>
> With RC1, maven tries to download this dependency
> org/apache/ws/commons/XmlSchema/SNAPSHOT/XmlSchema-SNAPSHOT.jar whereas with
> 2.0.9 it retreives the version 1.1.
> What I have is a project with a dependency to
> org.codehaus.xfire:xfire-core:1.2.6
> In the xfire-core pom we have a dependency to org.apache.ws.commons:XmlSchema
> The version 1.1 is set in the dependencyManagement of the parent.
> A testcase is attached
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
