Rafael Vanderlei wrote:
I'm just wondering if there is a suitable reason for that. So what I still
dont understand is "if a property declared in a parent pom can be used on
the child pom for other purposes, WHY cant it be used to activate a profile
defined in that child pom?"
Because profiles can define POM properties and considering POM
properties for profile activation would form a cycle. E.g., what
profiles are active and what's the effective value of the POM property
myProperty in this example:
<profiles>
<profile>
<id>one</id>
<activation>
<property>
<name>myProperty</name>
<value>foo</value>
</property>
</activation>
<properties>
<myProperty>bar</myProperty>
</properties>
</profile>
<profile>
<id>two</id>
<activation>
<property>
<name>myProperty</name>
<value>!foo</value>
</property>
</activation>
<properties>
<myProperty>foo</myProperty>
</properties>
</profile>
</profiles>
Feel free to share your description of a meaningful semantic for all
cases possibly arising from such a feature at
http://jira.codehaus.org/browse/MNG-5055.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
