Re: [PROPOSAL] Switch dependency managment to IVY

[David Crossley <cr...@apache.org>]

An old reply that i forgot to send ...

Ross Gardler wrote:
> Gav.... wrote:
> > Ross Gardler wrote:
> >>David Crossley wrote:
> >>
> >>>I see that you have Ivy module descriptors, e.g.
> >>>tools/ivy/repository/apache/xerces/ivy-2.5.0.xml
> >>>
> >>>Are these descriptors something that the Forrest
> >>>project maintains, or do we copy them from somewhere
> >>>else and thus need to keep them synchronised? I want
> >>>to clean them up to be consistent w.r.t. license stuff
> >>>etc. but not if they will come from some other project.
> >>>It seems to me that it is better to keep our own descriptors.
> >
> >I think the aim is that Ivy will update the license stuff in their
> >Public repo, they are now part of Apache and so I don't see why a
> >Transfer of license shouldn't take place. ...

I don't understand what you mean by "transfer of license".

These descriptors declare the license that is used by each
particular third-party product. 

> ... This would negate the
> >Need for us to update the license info I would have thought.
> >(Will check on that more thoroughly)
> 
> No, the aim is for us to pass a set of conf files to the ivy scratchpad 
> repository that work an are complete. It's our itch, we should scratch it.

Ah, that is what i wanted to know.
So we should tidy up these files here.

-David

> Besides, it is our PMC's responsibility to ensure our licence 
> information is valid.
> 
> >>Why not do it straight into the ivy scratchpad? Because I want Forrest
> >>devs to see how the ivy files are put together so that there is a
> >>history in our archives for people to manage the scratchpad/main reop
> >>over in Ivy.
> >
> >Don't most jars/dependencies come from Ivy/ibiblio anyway ? 
> 
> Some do, whether it will be most remains to be seen. Certainly, some 
> will not. Those that do not come from Ivy/Ibiblio need to be in our own 
> repo.
[ snip ]