On Thu, Jul 24, 2008 at 07:31:47AM +1200, Michael McCallum wrote: > On Thu, 24 Jul 2008 07:15:48 Thomas Darbois wrote: > > The best way to avoid that problem is to use a parent pom that define > > pluginmanagement so that each plugin used is clearly defined for your > > modules. > Thats not necessarily the best way! Its one way.
Thomas, Michael, thanks for your answers. I understand the interest of pluginManagement, unfortunately I have some "exotic" needs here: one of the module requires the assembly plugin version 2.1 one other module requires version 2.2-beta-1 and one other module requires version 2.2-beta-2 Indeed, they are some bugs in 2.1 that makes it unusable in some situations. These bugs have been fixed in 2.2-beta-1, but some regression (regarding interpolation) have been introduced. These regressions have been fixed in 2.2-beta-2, but some new regressions (regarding file duplications) have been introduced. Because we are using the assembly plugin in 3 different contexts and because all three versions have different bugs, we need to use all three different versions in the three modules. Would you know a way to do this? Regards, -- Julien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
