> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 15, 2004 9:08 PM
> To: Maven Users List
> Subject: RE: Maven and Development Process
>
> On Thu, 2004-04-15 at 17:05, Vincent Massol wrote:
> > > Maven2 support recursive inheritance well so would anyone still really
> > > need to use entities like this. Ultimately I suppose it doesn't matter
> > > how the POM comes together but I would like support to come from Maven
> > > itself and not the use of entities which I would consider a
> > workaround.
> >
> > I agree with this. However I'm not sure recursive inheritance is enough.
> > If we wish to support all use case, we'll need to support dependencies
> > reference as several projects may want to share some references while
> > they are not sharing exactly the same set of references. Putting all
> > references at the top level would mean that several subprojects which do
> > not need all these references will still inherit from them.
>
> Do you use this sort of setup?
>
> I think that the dep section would be expanded along the tree of POMs
> where needed. But one thing I was think about the POM structure was the
> possibility of a meta flag to indicate whether an element was overriden
> or aggregated. Still not sure if this would be necessary for this type
> of scenerio, but there will be some surveys coming along with the maven2
> alpha so we'll find out :-)
WDYT about flagging dependencies with free form attributes. Then
having an optional inclusion filter in every POM. This filter selects
the dependencies to include in the POM which is having its hierarchy
of dependencies determined dynamically. A filter can work like so:
(& (isRuntime=tree) (isOptional=true) )
If isRuntime and isOptional are dependency attributes then a
'defined' match can be determined. Otherwise a match is undefined when
these attributes are not present and the net effect is the same as a
failure to match.
Maven's dependency analyzing code can apply this filter to the
dependencies down the hierarchy until the super set of dependencies
are exhausted. So the effective dependency hierarchy can be controlled
using this filter and such free form attributes to express any
user's specific need.
WDYT?
--Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
