commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [PROPOSAL][all] Break dependency on commons-build
Date Sun, 12 Mar 2006 19:36:01 GMT
On 3/12/06, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On 3/12/06, Stephen Colebourne <scolebourne@btopenworld.com> wrote:
> > IIRC, we've been advised against overuse of svn:externals before. The
> > mechanism I've described is simple enough - just use the Internet for
> > what it was supposed to be used for. And no duplicated files at all.
>
> I agree that lots of svn:externals for each component would be a PITA
> - but if we put everything in a single directory in commons-build then
> that would be one per component, which once added shouldn't need to
> ever change. One svn:external per component isn't overuse IMO and is
> exactly what its designed for.
>
> +1 to Sandy's suggestion from me.

Biggest problem with svn externals is that they're not hooked into svn
moves. So have to be kept up to date when we move a component from one
place to another, or just change the svn url structure.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message