profile activation through properties fails

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.9
  • Fix Version/s: None
  • Component/s: dependencies task
  • Labels:
    None

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

Improvement - An improvement or enhancement to an existing feature or task. MANTTASKS-35 Support profiles in pom type

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
Paul Gier added a comment -

As a workaround, MANTTASKS-35 will 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.

Show
Paul Gier added a comment - As a workaround, MANTTASKS-35 will 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Richard Ziegler
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: