Unfortunately, Maven 2.0.x doesn't support that particular type of
profile activation. We're working on a feature in the trunk (2.1-
SNAPSHOT, currently) that would allow you to bring in custom profile
activators via build extensions, however. A custom activator could
give you an avenue for this sort of profile activation...but it's
still not available in a released version of Maven.
Sorry,
-john
On Aug 10, 2007, at 9:08 AM, Gisbert Amm wrote:
Michael Meyer schrieb:
Hi,
does this work?
<activation>
<property>
<name>project.packaging</name>
<value>war</value>
</property>
</activation>
Unfortunately not.
I'll describe my problem more generally instead of asking how to
fix my obviously wrong approach:
I need to execute a specific, home grown deployment preparation
plugin only for projects that produce a war (<packaging>war</
packaging>). How can I achieve that?
My first thought was to use a profile. However, that does not work
because a profile cannot be activated throught POM entries like
<packaging>war</packaging>. I don't want to set an extra property
for that either since all information I need is already covered in
the <packaging> element and doesn't need to be duplicated.
How do others implement conditional calls of certain plugins? How
is the Maven2 way to do that?
-Gisbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
