import-scoped dependencies of direct dependencies are not resolved using
profile modifications from settings.xml
----------------------------------------------------------------------------------------------------------------
Key: MNG-4347
URL: http://jira.codehaus.org/browse/MNG-4347
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories, Dependencies, General,
Profiles, Settings
Affects Versions: 2.2.1
Reporter: John Casey
Given:
* project A lists project B as a dependency
* project B lists project C as an import-scoped entry in dependencyManagement
* project B's dependency version for project C is a SNAPSHOT
* the user's settings.xml file modifies the definition of the central
repository to enable searching for SNAPSHOT artifacts.
When project A's dependency POMs are retrieved as part of collecting the
transitive dependency closure for A, B's project instance is built. During this
process, the POM for project C should be retrieved from central (according to
the modifications in settings.xml). However, the profile information from the
settings.xml is never applied to project B's POM, and never modifies the
central repository definition found there. Since the default definition for the
repository 'central' from the super POM has snapshots disabled, project C's POM
cannot be found, and the build fails.
--
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
