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

Craig McClanahan <[email protected]>
Newsgroups gmane.comp.jakarta.commons.user,gmane.text.xml.commons.devel
Message-ID <[email protected]>
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 current

The "svn propedit" command fires up your favorite editor on a multiple
line text file comprising the contents of the property.  Each line
contains the name of a subdirectory to create (under "current") and
the absolute URL of the corresponding SVN directory to be checked out.

Craig


On Sat, 29 Jan 2005 22:33:13 -0800, Craig McClanahan <[email protected]> wrote:
> 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 Proper and Commons Sandbox packages.
> 
> To check out the trunk (in CVS terms, the HEAD) branch of each Commons
> Proper and Commons Sandbox package, execute the following commands:
> 
>     mkdir /path/to/jakarta/commons/proper
>     cd /path/to/jakarta/commons/proper
>     svn checkout http://svn.apache.org/respos/asf/jakarta/commons/proper/current
>     mkdir /path/to/jakarta/commons/sandbox
>     cd /path/to/jakarta/commons/sandbox
>     svn checkout
> http://svn.apache.org/respos/asf/jakarta/commons/sandbox/current
> 
> A couple of notes:
> 
> * You can, of course, customize the "/path/to/jakarta/commons" part
>   of the paths above.
> 
> * Commons committers should use "https" in place of "http" in the
>   above URLs, so that you'll be able to do commits.
> 
> Craig McClanahan
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.