[MNG-5055] Allow to activate property-based profile by POM property

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.2.1, 3.0.3
• Environment: Tested with M3.0.2 and M2.2.1 on MacOS X (OS surely not relevant)
• Assignee: Unassigned
• Reporter: wolfgang häfelinger
• Created: 23/Mar/11 09:18
• Updated: 22/Jan/14 20:31
• Resolved: 22/Jan/14 20:31

Description

This demo consists of four file:
(1) README.txt
(2) pom.xml
(3) parent-pom.xml
(4) pom-no-profile-no-dep.xml

File" pom.xml" is the POM expected to activate profile "logging" defined in "parent-pom.xml". This does not work as clearly outlined in the original bug report MNG-3228 http://jira.codehaus.org/browse/MNG-3228.

File "pom-no-profile-no-dep.xml" is essentially the same as file "pom.xml". Section <dependencies /> and profile activation has been removed in order to get goal "help:effective-profiles" working.

The demo works like this: Install parent POM in local cache (~/.m2/repository).
% mvn -f parent-pom.xml install

Then try this:

Test 1:
% mvn -f pom.xml package
=> error

Test 2:
% mvn -f pom.xml package -Dactivate-profile-logging=true
=> good

Test 3:
% mvn -f pom.xml package -Plogging=true
=> good

Test 4:
% mvn -f pom-no-profile-no-dep.xml help:active-profiles
=> profile "logging" is not shown (expeced, but see next test)

Test 5:
% mvn -f pom-no-profile-no-dep.xml help:active-profiles -Dactivate-profile-logging=true
=> does not show profile "logging" although "logging" must be active (otherwise: why would second test work?)

Summary:
1. maven-help-plugin can't be trusted on reporting active profiles.
2. Activating inherited profiles differs from activating local profiles.

The second issue is clearly a design bug cause there is no good reason why inherited elements behave differently from local elements.

Issue Links

• is related to: MNG-3228 Maven profile activation does not work when profile is defined in inherited 'parent' pom