[MNG-2276] profile activation by property doesn't work with properties defined in settings.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.4
• Fix Version/s: 3.0-beta-1
• Component/s: POM, Profiles
• Assignee: Benjamin Bentmann
• Reporter: Brian E Fox
• Created: 05/May/06 08:17
• Updated: 10/Mar/16 13:54
• Resolved: 31/Mar/10 06:46

Description

Activating a profile like below doesn't get activated unless the property is set on the CLI. I need to have the property defined in the settings.xml so it's always set.
<profiles>
<profile>
<id>prod</id>
<activation>
<property>
<name>deploy-ct</name>
</property>
</activation>

Further, I noticed that if I set it so that the activation is like:
<activation>
<property>
<name>deploy-ct</name><value>true</value>
</property>
</activation>

The profile is triggered just by setting the cli like "mvn -Ddeploy-ct" It is not active if I use "-Ddeploy-ct=false" but the settings descriptor says that the existence of the property is only used if value is not set.

Issue Links

• is duplicated by: MNG-4088 [regression] settings.xml profiles are executed after project profiles
• is duplicated by: MNG-3614 settings.xml active profiles executed AFTER project profiles have been loaded and activated/not activated
• is related to: MNG-3309 Cascading profile activation
• is related to: MNG-1753 support improved property based profile activation
• is related to: MNG-2754 System Properties profile activation should move to Execution Properties activation