- Dan Diephouse
Jason van Zyl wrote:
Hi, As a result of splitting up the Jelly tag libraries the folks doing the split (Dion and others) discovered a need to share a set of common dependencies so as a result I've tentatively added the ability for a child to take it's parent's dependencies. The dependencies are the only place where this aggregation is happening as opposed to overriding inheritance.For me I know this will help in situations that involve building a set of components. Currently in Plexus there is a build and test for each component. There are JARs that are required for the tests to run, and prior to this change I had to declare the test time JARs in each of the components. So now I can define them in the parent and everything works just fine. This may bring up other problems during the copying of dependencies and I'm not sure what else, but it's in HEAD now so if it causes untold grief I'll back it out.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
