on 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 configu
Which parent properties would you want to propagate???
Martin
- Original Message -
From: "Brian E. Fox" <[EMAIL PROTECTED]>
To: "Maven Users List"
Sent: Wednesday, March 12, 2008 5:19 PM
Subject: RE: plugin configured across all maven 2 modules
Currently,
]
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 or
/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.
---
From: Wayne Fay [mailto:[EMAIL PROTECTED]
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 nee
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
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
