Spot on. BUT realize that you can't just add this configuration there and instantly expect all projects to pick it up...
You'll need to go into your parents (one level down from the updated corporate pom) and adjust the parent version, so they'll pick up the change. And that will probably require you to adjust the parent version in that level's children, etc on down. But this is a one-time change, assuming you aren't adjusting the top config very often. Unless of course you're using SNAPSHOTs for your top-leve corporate parent pom, which at least for us is pretty uncommon... Wayne On 3/12/08, Brian E. Fox <[EMAIL PROTECTED]> wrote: > All your projects should derive from an internal "corporate" pom that > acts as your internal super-pom in a sense. Then you can put things like > this that you want across your organization. > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2008 2:28 PM > To: users@maven.apache.org > Subject: plugin configured across all maven 2 modules > > Is there a way to configure a plugin across every module without > updating a million poms? > > We'd like to implement some of our validation plugins we wrote for all > poms and don't want to give people the option to NOT implement them. > > --------------------------------------------------------------------- > 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]
