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