[MANTTASKS-118] profile activation through properties fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.0.9
• Component/s: dependencies task
• Assignee: Unassigned
• Reporter: Richard Ziegler
• Created: 17/Sep/08 16:14
• Updated: 25/Nov/14 14:29
• Resolved: 25/Nov/14 14:29

Description

When using <artifact:pom file="pom.xml" ... , where the pom.xml has profiles with <activation> sections, the profiles are activated properly in the cases of:

• <activeByDefault>
• <jdk>
• <os>
• <file>

However, profiles that should be made active through <property><name>foo</name><value>true</value></property>, are not made active, even when invoking ant with -Dfoo=true.

Ideally property based activation would work with all ant properties, but the basic case is to support those explicitly set on the command line.

Issue Links

• is related to: MANTTASKS-35 Support profiles in pom type