On Wed, Sep 09, 2009 at 09:51:13AM +0100, sebb wrote: > Very few of the Maven plugins used by HC builds have their version > numbers specified. > > This means that builds are not necessarily reproducible/predictable. > > Rather than defining plugin versions within individual POMs, perhaps > it would be better to centralise the versions in the parent POM > pluginManagement section? > > If necessary, the version can be overridden by a child POM, but for > most (all?) plugins the version needs to be the same anyway. > > Note: this is what Apache Commons does; the parent POM defines all the > common plugin versions. > > Note that the pluginManagement section does not generate dependencies; > it only provides defaults. > > The section can also be used to provide other defaults, but obviously > that's only useful if these are universal. > > Views? > > I'd like to start with just Clover2, just in case this fixes the > Continuum builds. >
Sure. Please do so. The benefit of not explictly setting plugin versions is that, when upgrading to a newer release of Maven, 'core' plugins tested with that particular release get upgraded as well. It does make sense to fix versions of non-core plugins, though. Cheers Oleg > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
