maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Updated: (MNG-3052) Transitive Dependency not found when repo is not listed
Date Tue, 04 Nov 2008 19:32:51 GMT


Benjamin Bentmann updated MNG-3052:

    Fix Version/s: 2.0.10

> Transitive Dependency not found when repo is not listed
> -------------------------------------------------------
>                 Key: MNG-3052
>                 URL:
>             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, 2.1.0-M1
>         Attachments:,
> 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:
For more information on JIRA, see:


View raw message