M2. I suppose I will have to figure out a way to make sure mine gets loaded first. Are there any tricks out there for fooling the reactor?
On Tue, Apr 17, 2012 at 5:58 PM, Jörg Schaible <joerg.schai...@gmx.de>wrote: > Robert Egan wrote: > > > I have written a ContainerDescriptorHandler plugin for the Maven assembly > > plugin. It works when the module that uses it is built 'standalone'. When > > the module is built as part of a large multi-module project I see either > .... > > > > Does Maven have a switch to log the workings of the dependency mechanism > > as it does its job? > > > M2 or M3? For M2 the first error is normal, since every plugin is loaded > once and once only. If the first usage of the assembly plugin does not > contain your handler as part of its classpath, it will not be available > anywhere else in the multi-project build. M3 should instantiate the plugin > again with the proper CP. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
