maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-3603) Incomplete set of transitive dependencies resolved when transitive dependencies repository is not listed.
Date Wed, 02 Jul 2014 13:44:42 GMT

     [ https://jira.codehaus.org/browse/MNG-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Benedict updated MNG-3603:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Incomplete set of transitive dependencies resolved when transitive dependencies repository
is not listed.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-3603
>                 URL: https://jira.codehaus.org/browse/MNG-3603
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies
>    Affects Versions: 2.0.9
>         Environment: windows vista jdk 1.5.0_11
>            Reporter: Micah Whitacre
>         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 was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message