[
http://jira.codehaus.org/browse/MNG-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139809#action_139809
]
John Casey commented on MNG-3052:
---------------------------------
The problem is that the DefaultArtifactCollector is not using the repository
list aggregated and associated with each dependency is read via the
MavenMetadataSource...instead, it's using the repository list that was used to
resolve the declaring POM (the one that listed those dependencies).
I've corrected it and verified by hand that it works with the attached test
project, but I still need to convert the attached test project into a
self-contained integration-test project before I close this issue.
> Transitive Dependency not found when repo is not listed
> -------------------------------------------------------
>
> Key: MNG-3052
> URL: http://jira.codehaus.org/browse/MNG-3052
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Micah Whitacre
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.0.10
>
> Attachments: InheritLegacyRepo.zip, mng_3052.zip
>
>
> I have seen the situation where a build fails because a project has a
> transitive dependency that only exists in a repository not listed by my
> project. An example of this is I have Projects A, B, and C. Where A depends
> on B, and B on C. B has been released to remote repo 1, and C has been
> released to remote repo 2. Since A just directly depends on B it only lists
> remote repo 1 in its POM. However when I try to build project A the build
> fail because it can't resolve its transitive dependency C in any of the
> dependencies it is checking (repo 1 only).
> It is my understanding that for project A I shouldn't have to list the remote
> repos to resolve transitive dependencies. I should only have to list the
> repos to get to B and Maven then should use the POM of B to resolve C.
> Is that not correct?
--
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
