You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by EJ Ciramella <ej...@upromise.com> on 2008/03/12 19:27:32 UTC
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.
RE: plugin configured across all maven 2 modules
Posted by simon <si...@chello.at>.
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:brianf@reply.infinity.nu]
> 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:ejciramella@upromise.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin configured across all maven 2 modules
Posted by Martin Gainty <mg...@hotmail.com>.
Which parent properties would you want to propagate???
Martin
----- Original Message -----
From: "Brian E. Fox" <br...@reply.infinity.nu>
To: "Maven Users List" <us...@maven.apache.org>
Sent: Wednesday, March 12, 2008 5:19 PM
Subject: RE: plugin configured across all maven 2 modules
Currently, yes. You could play games with properties and stuff, but then
you get outside of repeatability.
-----Original Message-----
From: EJ Ciramella [mailto:ejciramella@upromise.com]
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:brianf@reply.infinity.nu]
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:ejciramella@upromise.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin configured across all maven 2 modules
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Currently, yes. You could play games with properties and stuff, but then
you get outside of repeatability.
-----Original Message-----
From: EJ Ciramella [mailto:ejciramella@upromise.com]
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:brianf@reply.infinity.nu]
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:ejciramella@upromise.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin configured across all maven 2 modules
Posted by EJ Ciramella <ej...@upromise.com>.
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:brianf@reply.infinity.nu]
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:ejciramella@upromise.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin configured across all maven 2 modules
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I tried snapshot parents once because I thought it was a good idea so I
wouldn't have to adjust all the parent poms. Take it from
experience...don't do that. Use release versions and only put the bare
minimum in the top so it doesn't change often.
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Wednesday, March 12, 2008 5:03 PM
To: Maven Users List
Subject: Re: plugin configured across all maven 2 modules
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 <br...@reply.infinity.nu> 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:ejciramella@upromise.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin configured across all maven 2 modules
Posted by Wayne Fay <wa...@gmail.com>.
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 <br...@reply.infinity.nu> 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:ejciramella@upromise.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin configured across all maven 2 modules
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:ejciramella@upromise.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org