Currently, yes. You could play games with properties and stuff, but then you get outside of repeatability.
-----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 6:16 PM To: Maven Users List; Maven Users List Subject: RE: plugin configured across all maven 2 modules But then if the plugin version changes, then we have to go through all the other poms that have a parent pom version and update them as well. Seems like an awful lot of work... Is this truly the only way? -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Wed 3/12/2008 2:57 PM To: Maven Users List Subject: RE: plugin configured across all maven 2 modules 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
