[ http://jira.codehaus.org/browse/MNG-757?page=all ]
John Casey closed MNG-757:
--------------------------
Resolution: Fixed
Fix Version: (was: 2.0-beta-2)
2.0-beta-1
see it0068 and it2001
> Transitive dependency resolution ignores custom repositories
> ------------------------------------------------------------
>
> Key: MNG-757
> URL: http://jira.codehaus.org/browse/MNG-757
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: Windows XP, Cygwin
> Reporter: Mark Hobson
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
> Attachments: projects.zip, settings.xml, test-repo.zip
>
> Original Estimate: 4 hours
> Time Spent: 2 hours
> Remaining: 0 minutes
>
> The attached files set the scene:
> * test-repo.zip - expand this into the root context of a local web server on
> 127.0.0.1:8080 for a test repo
> * projects.zip - expand this for the projects
> * settings.xml - the ~/.m2/settings.xml file
> The scenario is as follows:
> * test-repo contains a single artifact C
> * project B depends on C
> * project A depends on B & defines test-repo
> * settings.xml also defines test-repo
> The build process is:
> * m2 install B (downloads C, installs B ok)
> * m2 install A (finds B and C in local repo, installs A ok)
> Now the problem is if C is then deleted the second step fails - i.e. m2 only
> looks in the central repo for C and not the custom test-repo, even though
> test-repo is defined in both A's POM and settings.xml.
> This didn't happen in 2.0-alpha-3 - is this intentional?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
