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, Apaar Trivedi <[EMAIL PROTECTED]> wrote: > 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 module foo that > gets run using the default handler (nothing specified), then my next > module bar, which is built using a plugin we provided which configures > its own artifacthandler, doesnt seem to get that handler, hence it comes > out in the incorrect packaging type (this is howI know it's not using > the specific plugins handler.) > > > > But if i move module bar which uses the plugin with specific handler > before module foo, then it gets the correct packaging type (in this case > a zip file). > > > > Is this a known issue or what? > > > > Thanks > > Apaar Trivedi > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
