opensubscriber
   Find in this group all groups
 
Unknown more information…

d : dev@hc.apache.org 9 September 2009 • 4:51PM -0400

Define plugin versions in parent POM?
by sebb

REPLY TO AUTHOR
 
REPLY TO GROUP




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.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.a...
For additional commands, e-mail: dev-help@hc.a...

Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.