Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-3052

Transitive Dependency not found when repo is not listed

    XMLWordPrintableJSON

Details

    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?

      Attachments

        1. InheritLegacyRepo.zip
          5 kB
        2. mng_3052.zip
          4 kB
          Micah Whitacre

        Issue Links

          Activity

            People

              jdcasey John Dennis Casey
              mkwhitacre Micah Whitacre
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: