<snip a whole bunch> Jason said: I'm far more in favor of hosting a default snapshot repository on central and forcing plugin versions in 2.1. This creates far more stability and puts the onus on us to make finding that version for first time use easy. Not specifying a version for a plugin is not predictable as clearly shown with the last release of the surefire. If I had to specify surefire 2.2 then trunk would not have broken, or the 2.0.x branch. I think we should be striving for ease of use and stability.
--- I agree 100%. Anyone concerned about reproducibility would never allow the plugins to be unversioned in their builds. For my corp builds, it's as if this feature never existed...everything is in pluginMgt. I think if we are to encourage best practices, requiring a version somewhere, either in the plugin definition or pluginManagement is the right thing to do. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
