Option B doesn't make a whole lot of sense to me. Most people are interested in only a few commons projects so each having their own trunk, tags, and branches makes sense. Struts lays out its subprojects using Option A:
http://svn.apache.org/viewcvs.cgi/struts/ David --- Tim O'Brien <[EMAIL PROTECTED]> wrote: > I don't think we ever settled this question. > > Which SVN structure are we interested in? > > ** Option A: > > jakarta/ > commons/ > digester/ > trunk/ > tags/ > branches/ > beanutils/ > trunk/ > tags/ > branches/ > > OR > > ** Option B: > > jakarta/ > commons/ > trunk/ > digester/ > beanutils/ > tags/ > digester/ > beanutils/ > branches/ > digester/ > beanutils/ > __________________________________ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
