Hi, If your modules are depending upon a SNAPSHOT version of the parent, then just define this plugin in the parent and the modules will all see the new definition. Here, you've explicitly chosen configurability over repeatability.
If your modules are depending on a fixed version of the parent, then they will not automatically see this change; the module's parent reference needs to be changed. Here you've explicitly chosen repeatability over configurability. You cannot have both configurability (change parent, and all the children now immediately behave differently) and repeatability (the children builds act the same no matter what happens to the parent pom trunk version). Regards, Simon On Wed, 2008-03-12 at 18:15 -0400, EJ Ciramella wrote: > 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]
