"Noel J. Bergman" <[EMAIL PROTECTED]> writes:
>> 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.
So check out jakarta/commons/trunk/digester and work there.
Checking out the whole trunk is not the norm.
Folks, this is not CVS. You are not bound to a rigid structure as with
CVS. But you _want_ to be able to check out multiple projects side by
side. Because some of the depend on each other (or on the commons-site
module).
A major nit that I have to pick is the growing number of project
building with maven and the inability of _many_ maven plugins like the
changelog, dev or file activity lists to _use_ subversion. This is
actual information that we lose from the project sites if we go
subversion.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
What is more important to you...
[ ] Product Security
or [ ] Quality of Sales and Marketing Support
-- actual question from a Microsoft customer survey
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
