[
http://jira.codehaus.org/browse/MNG-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3603:
------------------------------
Fix Version/s: 2.0.x
> Incomplete set of transitive dependencies resolved when transitive
> dependencies repository is not listed.
> ---------------------------------------------------------------------------------------------------------
>
> Key: MNG-3603
> URL: http://jira.codehaus.org/browse/MNG-3603
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies
> Affects Versions: 2.0.9
> Environment: windows vista jdk 1.5.0_11
> Reporter: Micah Whitacre
> Fix For: 2.0.x
>
> Attachments: maven_testcase.zip
>
>
> I have project D which is dependent on project C. Project D lists the
> repository that the latest snapshot or release project C resides in. Project
> C depends on project B which depends on project A. Both projects B and A
> reside in a different repository than Project C and D. Project C properly
> lists the repository A and B reside in. All dependency scopes are compile so
> therefore transitively project D has a compile time dependency on A. The
> issue arises in that when building project D with a clean local maven
> repository project A is never resolved, no error is given but errors will
> occur later when actually trying to run tests.
> I have attached a testcase of this situation with projects A,B,C,and D. To
> duplicate this issue:
> 1. Unzip the attachment to a folder on your machine.
> 2. At the root of that folder run "mvn deploy". This will deploy projects A
> and B to fake-remote-repo2 and project C to fake-remote-repo1. One note is
> the URL of the repositories is windows based to this will need to be adjusted
> in the POMs and in the projectD pom if you are *nix based.
> 3. Clear your local maven repository.
> 4. Navigate to the "projectD" folder and run "mvn compile".
> After step 4 completes browse your local maven repo and you will notice that
> project A is not present.
> In the actual situation I'm encountering this it not only fails to resolve
> dependencies but also parent poms.
--
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
