I've had a similar issues when using different extensions that provide
lifecycles in the same build.
My solution was to write my own maven plugin that contained all the
lifecycles I needed (copy/paste from the original), and only use that
plugin as an extension.
On Wed, Apr 16, 2008 at 8:47 PM,
I have basically pasted this from the irc channel:
In a reactor, is it possible that the first artifacthandler that gets
used will be used for all subsequent modules that get run? Even if
those modules provide their own artifacthandler?
Because that is what's going on in my build. I have
If you're creating a new packaging/lifecycle for a specific type of
component you really get into a mess when you try to do it in-situ.
Just build it separately and then use it. What you're trying is not
specifically supported, if it works it's not intentional. Any
lifecycles or packaging
