The best practice is to at least specify the versions in pluginManagement. If you search the archives of this group, you will find lengthy discussions on this topic. The discussions specifically were around if we should require a version in 2.1 similar to how dependencies are handled.
-----Original Message----- From: Casey Butterworth [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 08, 2007 7:43 PM To: [email protected] Subject: Should all plugins have an explicit version? I recently raised issue http://jira.codehaus.org/browse/MNG-3142 MNG-3142 as there is a problem occuring when both a release and snapshot repo are defined and contain different versions of the same plugin, and LATEST is used as that plugin's version. I'm wondering if the parent pom (or wherever these plugins are defined) should contain an explicit version to avoid problems like this occurring in the future? FYI - the attached pom.xml will break an mvn clean, mvn compile, and probably a number of other default maven plugins. http://www.nabble.com/file/p12063865/pom.xml pom.xml -- View this message in context: http://www.nabble.com/Should-all-plugins-have-an-explicit-version--tf423 9703s177.html#a12063865 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]
