On 07/01/2008, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > > Hi, > > I just discovered that our multi-project build is unusable. The problem > seems to be that we use different versions of the same plugin throughout > our code base. When doing a multi project build (like using the > build.xml), only one version of the plugin is used for the whole build - > resulting in corrupt artifacts in the end. > The main problem atm is the maven-bundle-plugin; some modules use 1.0.0 > while others require 1.1.0-SNAPSHOT; it seems that at least on my > machine 1.0.0 is used everywhere.
yes, this seems to be a Maven limitation* wrt. multi-project builds, and if one project pulls in the 1.0.0 version then you could end up with bogus files in bundles (see the archived thread at http://www.mail-archive.com/[email protected]/msg02598.html for background) (* although this may just be a limitation wrt. mixing snapshot and released versions) last time I checked the 1.1.0-SNAPSHOT was used throughout trunk (see commit r605980) but the 1.0.0 version might well have snuck back in... once the bundleplugin is released we could use 1.1.0 throughout, and centralize the version as a property in the parent pom ** I think that this is a known problem of m2 - and I don't see a good > solution for this. Using different versions of plugins in different > modules makes sense as we have different release cycles (well at least > that's the plan). So the only working solution right now seems to be to > build module by module separately. yes, although releasing 1.1.0 might help with this, as we won't depend on plugin snapshots Carsten > -- > Carsten Ziegeler > [EMAIL PROTECTED] > -- Cheers, Stuart
