[ http://jira.codehaus.org/browse/MNG-757?page=comments#action_44935 ]
John Casey commented on MNG-757: -------------------------------- this would seem to imply that we expect dependency poms to have profiles from settings.xml merged into them...that doesn't sound right to me. The only way that a could transitively find c would be if: 1. the same set of repositories were used at all levels for dependency resolution...which would be defined in the project-to-be-built pom.xml file. This is how -alpha-3 worked. 2. we apply settings.xml profiles to all POMs we work with during the build, including dependency POMs. If you think about the integrity of the dependency POM, these two are restatements of the same thing...modifying something that's meant to be an authoritative source of information for a graph of dependencies (the dependency and it's transitive closure). I'm not sure it's wise to put all resolution control in the hands of your project's dependencies...so maybe it would be better to say that the project being built should provide the list of repositories used to resolve everything a la -alpha-3...? I bring this up since there was another JIRA issue filed to change that to repository-set-per-POM. > 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 > > > 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]
