RE: [all] correction was RE: [ALL] Checking Out Trunk Of All Commons Packages

2005-01-30 Thread Tim O'Brien
PM > To: Jakarta Commons Users List > Cc: Jakarta Commons Developers List > Subject: Re: [all] correction was RE: [ALL] Checking Out > Trunk Of All Commons Packages > > I try to follow these lists, but Gmail's spam filter ate > these and I didn't see them :-(. G

Re: [all] correction was RE: [ALL] Checking Out Trunk Of All Commons Packages

2005-01-30 Thread Craig McClanahan
rta-commons-sandbox > > Tim O'Brien > > > -Original Message- > > From: Craig McClanahan [mailto:[EMAIL PROTECTED] > > Sent: Sunday, January 30, 2005 12:33 AM > > To: Jakarta Commons Developers List; Jakarta Commons Users List > > Subject: [ALL] Chec

[all] correction was RE: [ALL] Checking Out Trunk Of All Commons Packages

2005-01-30 Thread Tim O'Brien
O'Brien > -Original Message- > From: Craig McClanahan [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 30, 2005 12:33 AM > To: Jakarta Commons Developers List; Jakarta Commons Users List > Subject: [ALL] Checking Out Trunk Of All Commons Packages > > Marti

Re: [ALL] Checking Out Trunk Of All Commons Packages

2005-01-29 Thread Craig McClanahan
I should mention how you update the list of packages that are included, for when new Commons Proper or Commons Sandbox packages are added later: cd /path/to/jakarta/commons/proper svn propedit svn:externals current cd /path/to/jakarta/commons/sandbox svn propedit svn:externals cur

[ALL] Checking Out Trunk Of All Commons Packages

2005-01-29 Thread Craig McClanahan
Martin Cooper took advantage of an ability of Subversion (after being pointed at it by Tim O'Brien -- thanks Tim and Martin!) to use the "svn:externals" capability to create a pseudo-directory of the trunk subdirectory for each Struts subproject. I've implemented the same technique for Commons Pro