maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <>
Subject [jira] (MNG-5673) Profile activation does not work if more than 1 type of activation is present
Date Tue, 12 Aug 2014 00:20:10 GMT


Jason van Zyl commented on MNG-5673:

This change will not be reverted. There was conflicting documentation but I believe this is
the right behaviour. Occassionally we make changes that break some things. There is only one
way to specify profiles right now and it's not possible currently to implement custom activators.
As such this mode where it is possible to AND and OR is preferred only only being able to
to OR. When custom profile activators can be added I will make an implementation using MVEL
which will be more flexible.

> Profile activation does not work if more than 1 type of activation is present
> -----------------------------------------------------------------------------
>                 Key: MNG-5673
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: Documentation: Guides, Profiles
>    Affects Versions: 3.2.2
>            Reporter: Jeroen Ruijgers
>            Priority: Blocker
> When a profile has more than 1 activation, according to the [documentation|]
1 match is enough to activate a profile:
> {quote}Activation occurs when one or more of the specified criteria have been met. When
the first positive result is encountered, processing stops and the profile is marked as active.{quote}
> Since Maven 3.2.2 this does not work. For instance with the following activation code:
> {code}
>             <activation>
>                 <file>
>                     <exists>${env.JBOSS_HOME}/server/development</exists>
>                 </file>
>                 <property>
>                     <name>assembly</name>
>                 </property>
>             </activation>
> {code}
> The profile only gets activated if both the directory is present and the propery is specified.
If we remove the property from the configuration, the profile is activated based on the directory

This message was sent by Atlassian JIRA

View raw message