I'll argue that even in the cvs case, it usually doesn't make any logical sense to checkout the entire commons as one checkout, many of the components are organized to be mounted as separate projects in an IDE such as Eclipse. As such they need to be individually checked out and mounted as projects in Eclipse. With the Repository Browsing perspective in Eclipse, you can do this for multiple projects with the greatest of ease. I suspect its going to be just as easy to do this with SubEclipse.
-Mark
Noel J. Bergman wrote:
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.
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
