commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: HELP! - WAS: Re: [vote][net] Release commons-net 1.4.1?
Date Mon, 05 Dec 2005 18:40:37 GMT
Dennis Lundberg wrote:

>If commons component A extends the project.xml file from commons-build 
>these dependencies are transfered to that component, meaning that 
>component A doesn't have to worry about dependencies for site generation.
>However, if commons component B does *not* extend the project.xml file 
>from commons-build these dependencies will have to be repeated in the 
>project.xml file for component B. Hopefully these dependencies would not 
>change all that often, meaning that little work would have to be done in 
>order to keep this working, once it has been set up properly.
>Either way I think there is a big win including these dependencies in 
>commons-build and all commons components. What do you think?

This sounds great.  Would have made my tasks this weekend much easier.

However, I'm a bit behind the maven curve here.  Could you please
explain what the "extends" mechanism is for POMs?  How would I tell if
the project I'm working on extends commons-build or not?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message