[
http://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264310#action_264310
]
Eric Pabst commented on MNG-4565:
---------------------------------
I have a fix for this here:
https://github.com/epabst/maven-3/tree/MNG-4516
> Multiple profile activation conditions does not work
> ----------------------------------------------------
>
> Key: MNG-4565
> URL: http://jira.codehaus.org/browse/MNG-4565
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.2.1
> Environment: All platforms.
> Reporter: Nicholas Allen
> Fix For: Issues to be reviewed for 3.x
>
>
> According to the documentation at
> http://www.sonatype.com/books/mvnref-book/reference/profiles-sect-activation.html
> a profile is activated when all activation conditions are met (which makes
> sense of course). But when I try to use this it does not work. It seems maven
> does an OR instead of an AND (which is not rearly as useful and is the
> opposite of what the documentation says at the previous link).
> For example, if I have one profile that is activated like this:
> <activation>
> <activeByDefault>false</activeByDefault>
> <os>
> <name>linux</name>
> </os>
> </activation>
> and another profile that is activated like this:
> <activation>
> <activeByDefault>false</activeByDefault>
> <os>
> <name>linux</name>
> </os>
> <property>
> <name>release</name>
> <value>true</value>
> </property>
> </activation>
> Then I would expect the second profile to only be activated if the OS is
> linux and the release property is defined.
> When I run 'mvn help:active-profiles' however, maven shows that both profiles
> are active even though the release property is not defined.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
