Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.9
-
Fix Version/s: None
-
Component/s: dependencies task
-
Labels:None
-
Number of attachments :
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
-
As a workaround,
MANTTASKS-35will allow you to activate profiles for a pom. But you would still have to do the work in ant of passing the properties to the profile configuration.