parent pom can't change in it's basic "build required" info (eg.
dependencies), but we can add more info like license, url,...
it's better to centralize it than have it copied all over
On 10/30/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 10/30/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> There are a lot of common things to all eclipse projects like license.
> Having the license all over all projects is not easy fo fix,
> change,... Same problem for all common info
but given the actual repository policy, also the parent pom can't
change: if you fix the license in the parent pom you will have to
deploy a new version and update all the children pom to use a
different parent. And since all the poms are automatically generated
by the eclipse plugin I can't see a big difference here...
fabrizio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
