You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/06/12 08:56:10 UTC
[jira] (MNG-5619) CLONE - Multiple profile activation conditions
broken
[ https://jira.codehaus.org/browse/MNG-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347903#comment-347903 ]
Jason van Zyl commented on MNG-5619:
------------------------------------
Fixed as per MNG-4565
> CLONE - Multiple profile activation conditions broken
> -----------------------------------------------------
>
> Key: MNG-5619
> URL: https://jira.codehaus.org/browse/MNG-5619
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.2.1, 3.0.5
> Reporter: SebbASF
> Assignee: Paul Gier
> Fix For: 2.0.10
>
>
> Having multiple profile activation conditions behaves in an unexpected manner. It doesn't cause a build failure, but the actual algorithm for activating a profile is very different from expected. My expectation was that if you include multiple conditions, they are ANDed together. However what appears to happen is that the conditions overwrite each other.
> If an <os> condition is added, it overrides any <property> or <file> conditions regardless of their results.
> If a <file> condition is added, it overrides any <property> condition regardless of results
> The following table gives a sample of conditions matched, and whether the profile was activated as a result:
> Property File OS Result Expected
> T T - T T
> T F - F F
> F T - T F
> F F - F F
> T - T T T
> T - F F F
> F - T T F
> F - F F F
> F F T T F
> T T F F F
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)