Yes, the pluginManagement tag will do this. Of course if you change the setting in a parent pom, all the child poms need to be updated to point to the new parent pom before this will take effect. If the child modules point to different versions of the parent pom, then they will still be using different versions of the plugin.
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? Of course if you have a company policy of using only specific "approved" versions of libs or plugins, then the way to achieve that is to set up your own repository with only the allowed artifacts in it, and then use that instead of the public repos (using <mirrorOf>*</mirrorOf>). Regards, Simon nicolas de loof schrieb: > Use <pluginManagement> in your parent POM ! > > 2008/4/3, Farrukh Najmi <[EMAIL PROTECTED]>: > >> Dear Colleagues, >> >> Is there a way to centrally control the version of a plugin by specifying >> something like dependencyManagement in top-level project pom so the plugin >> versions are not specified in all sub-module poms? >> Reading archives suggest this is not possible but I wanted to make sure. >> TIA for your help. >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
