[MNG-776] settings.xml profile activation breaks reactor

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-1
• Environment: Windows XP, Cygwin
• Assignee: Unassigned
• Reporter: Mark Hobson
• Created: 23/Aug/05 06:41
• Updated: 08/Feb/20 15:40
• Resolved: 23/Aug/05 09:52

Description

The attached zip consists of:

1) Parent POM project A
2) Child JAR project B
3) settings.xml

Running m2 in the 'a' dir:

m2 -s ../settings.xml install

Results in a failed build - m2 looks for B's POM at a/b/b/pom.xml rather than a/b/pom.xml.

Issue Links

• is related to: MNG-773 profiles applied to POM inheritance hierarchy will pollute child POMs with modules from parents