commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <>
Subject RE: Jakarta Commons Structure rehashed
Date Mon, 20 Dec 2004 05:20:36 GMT
On Mon, 2004-12-20 at 08:36, Tim O'Brien wrote:
> > -----Original Message-----
> > From: Martin Cooper [] 
> > I think we're trying to find a compromise that satisfies 
> > both. As long as someone can come up with a way to do the 
> > equivalent of the '*' URL I mentioned above, I'd be happy 
> > with A + that script / tool / method.
> Add, externals definitions to that list.
> Assume that /jakarta/commons/proper/current is just a directory with
> externals to every trunk for components in commons proper, and
> /jakarta/commons/sandbox/current is just a directory with externals to
> every trunk for sandbox components.  I could also see someone wanted to
> checkout only the current production release of every component, we
> could similarly have a /jakarta/commons/proper/production which would
> contain externals pointing to the latest official release tag.
> See section 7.3 "External Definitions" of Version Control with
> Subversion by Collins-Sussman, Fitzpatrick, and Pilato.  You can read
> that book on Safari or online for free here:


That seems like a good solution to me. The projects are then nicely
self-contained, but people learning commons, or tools that scan the
whole of commons (eg automated license checkers or gump-like tools) can
get access to the latest code of all projects via proper/current. 

Setting up a proper/production might be a bit trickier (or at least
ensuring it *stays* pointing to the right target dir).

NB: It was me who raised the issue of "being able to check out HEAD of
all projects" in the first place..



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

View raw message