maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-4565) Multiple profile activation conditions does not work
Date Thu, 12 Jun 2014 01:35:14 GMT

     [ https://jira.codehaus.org/browse/MNG-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason van Zyl closed MNG-4565.
------------------------------

    Resolution: Fixed
      Assignee: Jason van Zyl  (was: brianfox brianfox)

> Multiple profile activation conditions does not work
> ----------------------------------------------------
>
>                 Key: MNG-4565
>                 URL: https://jira.codehaus.org/browse/MNG-4565
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Profiles
>    Affects Versions: 2.2.1, 3.2.1
>         Environment: All platforms.
>            Reporter: Nicholas Allen
>            Assignee: Jason van Zyl
>             Fix For: 3.2.2
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message