[MNG-4106] [regression] Interpolation does not use properties from dominant settings profile if other profile defines same property

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-alpha-3
• Fix Version/s: 3.0-alpha-3
• Component/s: Inheritance and Interpolation
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 23/Mar/09 16:49
• Updated: 24/Mar/09 09:04
• Resolved: 23/Mar/09 18:04

Description

For two or more profiles in the {{settings.xml}

<profiles>
  <profile>
    <id>settings-a</id>
    <properties>
      <settingsProperty>a</settingsProperty>
    </properties>
  </profile>
  <profile>
    <id>settings-b</id>
    <properties>
      <settingsProperty>b</settingsProperty>
    </properties>
  </profile>
</profiles>

the expression ${settingsProperty} will resolve to "a" although the later profile is dominant (noticeable at the POM property (not expression!) settingsProperty being "b" in the effective POM).

Issue Links

• depends upon: MNG-2309 Profile activation order is random
• relates to: MNG-4107 [regression] User settings can't override properties used for POM interpolation