>I personally think using <pluginManagement> to impose the same version >on a bunch of other modules is a bad idea anyway. You cannot control >what plugin versions are used by third-party libraries - and don't care, >right? So why try to impose this on your own code? If a module >successfully builds and passes its unit tests with version X of a plugin >then why does it matter if this is not the latest version, or is >different from the version used by something else?
This is the completely not what we suggest. First of all you don't care what 3rd parties use for plugins as those plugins are only used in their build, not yours. Assuming you see their jar, then their build succeeded. If you don't lock down your plugin versions, then you are subjected to plugin changes over time and your builds won't be reproducible. Further, if you haven't specified a preference, then there's no way to ensure consistency across your team. We have addressed the random plugin updates in 2.0.9 by specifying default versions for plugins but we still recommend that you take control of the plugin versions yourself. This way you will be able to go back and build a version at some point in the future and changing Maven versions won't upgrade all your plugins at once. --Brian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
