Allow multiple profile activation properties.

Maybe adding support for boolean operators would be nice. Here is an example:

—
<activation>

<and>
<property><name>prop-1</name></property>

<property><name>prop-2</name></property>

<property><name>prop-3</name></property>

<or>
<property><name>prop-4</name></property>

<not>
<property><name>prop-5</name></property>
</not>

<property><name>prop-6</name></property>

<os>MacOS</os>

</or>

</and>

</activation>
—

For better compatibility with the current maven model, the syntax for this should look more like this:

<activation>
  <property>
    <name>my-prop-1</name>
    <value>some-value</value>
  </property>
  <property>
    <name>my-prop-2</name>
    <value>another-value</value>
  </property>
</activation>

If either of these properties match the given value, the profile should be activated.
In addition, the other activators (os, jvm, file, etc) should also be allowed to have multiple values.

boolean operators could be achieved with the following syntax (let's assume with want to express the condition ((a && b) || (c && d)) )

<activations>
  <activation>
    <properties>
      <property>
        <name>my-prop-A</name>
        <value>valueA</value>
      </property>
      <property>
        <name>my-prop-B</name>
        <value>valueB</value>
      </property>
    </properties>
  </activation>
  <activation>
    <properties>
      <property>
        <name>my-prop-C</name>
        <value>valueC</value>
      </property>
      <property>
        <name>my-prop-D</name>
        <value>valueD</value>
      </property>
   </properties>
  </activation>
</activations> 

so all the conditions within one activation are considered as an AND and the different activation elements are considered as an OR. The downside of this proposal is of course that it would break the current POM model.

Activating a profile based on EITHER property matching the given values is already possible, just copy the profile. If you want to avoid duplication simply use XML entities. What is not currently possible is to activate a profile based on ALL properties matching the given values.

I would like that the following snippet meant "if all properties match the given values, the profile should be activated".

<activation>
  <property>
    <name>my-prop-1</name>
    <value>some-value</value>
  </property>
  <property>
    <name>my-prop-2</name>
    <value>another-value</value>
  </property>
</activation>

Would be great if you could marry OS and Properties as an AND condition.

For example,

   <activation>
     <os>
       <family>unix</family>
     </os>
     <property>
       <name>my-prop-2</name>
       <value>another-value</value>
     </property>
   </activation>
 

Currently, Maven2 looks for the first condition that is true, and the profile is activated. However, this is not very useful if the build needs to run in both Windows and Unix environments and you need to do something slightly different on each OS, where activation is also determined by a property being set at buld time

+1 to Elifarley Callado Coelho for boolean logic,
-1 to Marco Sandrini for too verbose syntax.

This issue makes our cross-platform build a mess, tracked as

Maven profiles appear not to be able to fully discriminate MacOSX 10.6.x, Apple JDK 1.6.x, x86_64
http://code.google.com/p/piccolo2d/issues/detail?id=151

Why is an enhancement with this many votes being ignored? What is the reason that this is not being considered or scheduled in the pipeline?

This request was first entered 3 years ago, when will it ever be honored? I think this is something many developers are waiting for...

I posted a fix for MNG-4516, which is related.

So, will this one be any time soon?

Same problem here!
Costs me days now, to find a workaround, if that is possible.

What sense does that AND condition make? You could do every AND with several profiles.
But tell me, is there ANY chance to do an OR condition, as it is described in MNG-4516?

Bug was for 2.0.8, I'm using 2.2.1 and 3.0.3 and nothing got better ...

+1 for conditional operators, especially OR. I could really use this!

Just noticed that, as of this writing, this issue is #5 in popularity:
http://jira.codehaus.org/browse/MNG#selectedTab=com.atlassian.jira.plugin.system.project%3Apopularissues-panel

Can the project get this resourced?

Guys this defect is 5 years old now. What the hell are you waiting for ?