A concrete manifestation of this problem is outlined here:
http://forums.atlassian.com/thread.jspa?messageID=257293240
Ideally - could we add another sub-element to the <execution> element
which decides whether or not to merge the configuration defined in the
profile with that in the default definition, <merge/> ?
What are your thoughts on adding another option for this? I am
guessing other plugins will also not want to merge <executions> from
profiles.
Cheers,
Nick
On 11/11/2008, at 11:39 AM, Nick Pellow wrote:
Hi Brian,
Even changing the executions to something else doesn't appear to work.
Is there anything my plugin can do, to prevent the executions in the
default plugin definition being merged with those defined in a
profile?
Cheers,
Nick
On 30/10/2008, at 12:49 AM, Brian Fox wrote:
You can't unset something like that because it appears null and the
merge will overwrite it. You could change it to something else though
--Brian (mobile)
On Oct 29, 2008, at 1:49 AM, Nick Pellow <[EMAIL PROTECTED]>
wrote:
Hi,
If a plugin is defined in the normal build section of a pom and
has defined a specific execution, is it possible to override this
execution by defining the same plugin in a profile?
The plugin I am working on, uses a forked build lifecycle, so when
I try to do this, I see the executions defined outside the profile
being run, as well as those defined in the profile. Ideally, I'd
like the executions defined for the plugin outside the profile
completely ignored when the profile is activated.
e.g.
<build>
<plugins>
<plugin>
<artifactId>plugin</artifactId>
<executions>
<execution>
<id>execution1</id>
<phase>verify</phase>
<goals>
<goal>goal1</goal>
<goal>goal2r</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
and then inside a profile:
<profiles>
<profile>
<build>
<plugins>
<plugin>
<artifactId>plugin</artifactId>
<executions>
<execution>
<id>execution1</id>
<phase>verify</phase>
<goals>
<!-- no goals -->
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
Cheers,
Nick Pellow
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
