commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jelly] Re: Inheriting Dependencies
Date Sun, 26 Jan 2003 14:31:37 GMT
I'll test this and the reactor, as it means we can do away with:
1) The included entity in all project.xmls
2) The ant build-all file
and have an easy way to do things to all taglibs at once, e.g.
- Regen gump descriptor
- Regen ant build file
- Build jars etc
dIon Gillard, Multitask Consulting

Jason van Zyl <> wrote on 25/01/2003 02:09:55 AM:

> 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.
> -- 
> jvz.
> Jason van Zyl
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>   -- Jacques Ellul, The Technological Society
> --
> To unsubscribe, e-mail:   <mailto:turbine-maven-user-
> For additional commands, e-mail: <mailto:turbine-maven-user-

> ForwardSourceID:NT000A809E 

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

View raw message