[MNG-4347] import-scoped dependencies of direct dependencies are not resolved using profile modifications from settings.xml

[jira-importer]

John Dennis Casey opened MNG-4347 and commented

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.

---

Affects: 2.2.1

Issue Links:

• MNG-6772 Super POM overwrites remapped central repository in nested dependencyManagement import POMs

• MNG-4645 Move Central repo definition out of Maven's jars so it can be more easily changed

• MNG-4148 Apply profiles from settings.xml to POMs built from the repository

Remote Links:

• Page
  
• GitHub Pull Request #158
  
• GitHub Pull Request #159
  

Backported to: 2.2.2

1 votes, 6 watchers

[jira-importer]

John Dennis Casey commented

Started work on https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x-MNG-4347 to isolate changes. The general approach is to make a session-specific MavenMetadataSource instance that can pass the global profile manager throughout the resolution process, so those profiles can be used to modify the definition of the central repository or others as specified.

[jira-importer]

Christian Schulte commented

Issue is fixed in the master branch of my private maven repository on github. When interested, you can cherry pick the commit to your own repository and create a pull request for the apache master branch with just this commit yourself from there.

[jira-importer]

Clark Perkins commented

Sorry for all the extra comments above, I should have looked for this issue here before just trying to fix the issue and open a PR.

[jira-importer]

Michael Osipov commented

I believe this is related to MNG-6772 and may be resolved when MNG-4645 is completed.