Re: Jakarta Commons Structure rehashed

[Stephen Colebourne]

I may know nothing about SVN yet, but it would seem that we should treat 
each component as relatively independent. Releases and versioning freqently 
occur at that level. Needing to get the entire repository is a rare task.
Stephen
----- Original Message ----- 
From: "Tim O'Brien" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, December 19, 2004 7:14 AM
Subject: RE: Jakarta Commons Structure rehashed



-----Original Message-----
From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 18, 2004 11:12 PM
To: Jakarta Commons Developers List
Subject: RE: Jakarta Commons Structure rehashed
> I also prefer the flatter layout:
> jakarta/commons/tags/
>                /branches
>                /trunk
We don't version Commons as a single component, and I don't
know that we want to force everyone to always take every
single component.  Someone wanting to build all of Commons is
not the norm.
Agreed, we also don't want to go through the acrobatics of maintaining a
jakarta/commons/tags directory with hundreds of subdirectories.  Think
about just how many tags we have in commons and then contemplate a
single directory with every <component_name>-<tag> combination, that's
going to get silly very fast.  Likewise for branches.
Each component in commons proper is a component digester has a trunk, it
gets tagged, and branches independently of latka.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]