Maven 2 & 3

support improved property based profile activation

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: POM, Profiles
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

support better profile activation via

a) multiple property elements in the activation element.

eg:-

<activation>
<property>
<name>os.name</name>
<valueWindows XP</value>
</property>
<property>
<name>os.name</name>
<valueWindows 2000</value>
</property>
</activation>

b) regex based property parsing for both name and value elements (dont know how you'll want to handle the tagging to indicate that something is a regex property rather than a plain one but for now im using regexName and regexValue)

eg:-

<activation>
<regexProperty>
<name>os.name</name>
<regexValue>Windows 2000|Windows XP</regexValue>
</property>
</activation>

same for name.

Issue Links

Activity

Hide
Brett Porter added a comment -

we're currently taking submissions for the new features to accept for 2.1 development - if you'd like to fill in a proposal please drop this in there - thanks!

Show
Brett Porter added a comment - we're currently taking submissions for the new features to accept for 2.1 development - if you'd like to fill in a proposal please drop this in there - thanks!
Hide
Michael Mellenthin added a comment -

We need profile activation per workset. A possible solution is to activate a profile in settings.xml by property. We don't want to set a system property but rather add a property in pom.xml. Is it planned to support this feature in 2.1 or only in 3.x?

Show
Michael Mellenthin added a comment - We need profile activation per workset. A possible solution is to activate a profile in settings.xml by property. We don't want to set a system property but rather add a property in pom.xml. Is it planned to support this feature in 2.1 or only in 3.x?
Hide
jieryn added a comment -

Please supply profile activation based on whether or not this build is a development line or not, e.g. containing -SNAPSHOT in the $project.version. This may be covered by the regexProperty suggestion above, but perhaps is worthwhile as its own first class activation citizen.

Show
jieryn added a comment - Please supply profile activation based on whether or not this build is a development line or not, e.g. containing -SNAPSHOT in the $project.version. This may be covered by the regexProperty suggestion above, but perhaps is worthwhile as its own first class activation citizen.
Hide
jieryn added a comment -

Please supply profile activation based on the packaging type for this build, e.g. pom, jar, war, etc.

Show
jieryn added a comment - Please supply profile activation based on the packaging type for this build, e.g. pom, jar, war, etc.
Hide
jieryn added a comment -

Please supply profile activation based on whether maven is in offline mode.

Show
jieryn added a comment - Please supply profile activation based on whether maven is in offline mode.
Hide
jieryn added a comment -

Please supply profile activation based on properties set within the pom.xml, or its parents, via project.properties. Currently, only properties passed on the CLI are able to activate profiles.

Show
jieryn added a comment - Please supply profile activation based on properties set within the pom.xml, or its parents, via project.properties. Currently, only properties passed on the CLI are able to activate profiles.

People

Vote (18)
Watch (14)

Dates

  • Created:
    Updated:
    Resolved: