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

• Type: Bug
• Status: Reopened
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.2.1
• Fix Version/s: 2.2.2, 4.0.x-candidate
• Component/s: Artifacts and Repositories, Dependencies, General, Profiles, Settings
• Assignee: Unassigned
• Reporter: John Dennis Casey
• Created: 08/Sep/09 18:25
• Updated: 13/Mar/21 17:20

Description

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.

Issue Links

• is related to: MNG-6772 Super POM overwrites remapped central repository in nested dependencyManagement import POMs
• is related to: MNG-4645 Move Central repo definition out of Maven's jars so it can be more easily changed
• relates to: MNG-4148 Apply profiles from settings.xml to POMs built from the repository
• links to: GitHub Pull Request #158
• links to: GitHub Pull Request #159
• mentioned in: Page Loading...