In my opinion, yes. In my corporate builds, I lock down ALL versions of plugins used by the lifecycles or bound in a pom. I do this for 3 reasons: consistency across the development team, reproducibility in the future, and stability. This allows my CM team to validate a new plugin before deciding to roll it out. We use a single root parent from which all our projects derive, this allows us to maintain it in one place.
-----Original Message----- From: Casey Butterworth [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 8:34 PM To: [email protected] Subject: RE: Should all plugins have an explicit version? Brian E. Fox wrote: > > The best practice is to at least specify the versions in pluginManagement. > Brian - would this approach hold true for all plugins (e.g. clean, compile, install, etc?) -- View this message in context: http://www.nabble.com/Should-all-plugins-have-an-explicit-version--tf423 9703s177.html#a12064413 Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
