[EMAIL PROTECTED] wrote:
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?
Maven's POM extends works pretty much like extends in Java. Define stuff
you want to reuse in the parent and then use in the child. If you don't
like what's in the parent just override it in the child.
You can tell if your component is extending commons-build by looking at
the top of your component's POM. If you find this line there:
<extend>../commons-build/project.xml</extend>
then it's extending commons-build.
A quick look in my, just updated, SVN checkout of commons-proper shows
that only commons-attributes and commons-chain are extending commons-build.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
