Details
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
- depends upon
-
MNG-4153
Profile activation based on module in development status (i.e. -SNAPSHOT)
-
-
MNG-4154
Profile activation based on module packaging type (e.g. jar, war, ear)
-
-
MNG-4155
Profile activation based on Maven offline-mode status
-
- duplicates
-
MNG-3826
Add profile activation when project version matches a regex
-
-
MNG-3328
Allow multiple profile activation properties.
-
- is related to
-
MNG-4516
Contradiction between the documentation and Maven's behavior related to profile-activation with multiple criteria
-
-
MNG-3106
Multiple profile activation conditions broken
-
- relates to
-
MNG-4516
Contradiction between the documentation and Maven's behavior related to profile-activation with multiple criteria
-
-
MNG-4565
Multiple profile activation conditions does not work
-
-
MNG-2276
profile activation by property doesn't work with properties defined in settings.
-
-
MNG-2848
Environment variables in profile activation not working
-
-
MNG-3106
Multiple profile activation conditions broken
-
-
MNG-3328
Allow multiple profile activation properties.
-
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!