[MNG-3052] Transitive Dependency not found when repo is not listed

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.5
• Fix Version/s: 2.0.10, 2.1.0-M1
• Component/s: Artifacts and Repositories
• Assignee: John Dennis Casey
• Reporter: Micah Whitacre
• Created: 13/Jun/07 13:09
• Updated: 04/Nov/08 13:32
• Resolved: 27/Jun/08 11:43

Description

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?

Issue Links

• is related to: MNG-3056 Dependencies should not be able to introduce repositories to the build