Related link: https://svn.apache.org/repos/asf/jakarta/commons
Jakarta Commons just moved over to Subversion, and because a fair number of projects depend on Commons, I thought I’d tell people how to check it out properly. Just in case someone depends on commons and isn’t subscribed (or paying attention) to the dev list, here are some simple instructions:
svn co https://svn.apache.org/repos/asf/jakarta/commons/trunks-proper jakarta-commons
svn co https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox jakarta-commons-sandbox
If you execute either one of these commands you will have the same working environment you had with
cvs co jakarta-commons or
cvs co jakarta-commons-sandbox. Only committers need to do this over https, so, if you are just checking it out with no intention of contributing, please save us some CPU cycles and use http (although the externals are set to https). The
trunks-sandbox directories have the
svn:externals property set to point to the trunks of all proper and sandbox components.
svn:externals is an interesting part of Subversion, and you can read more about it in the Subversion book. To get a list of all of the externals, run:
svn propget svn:externals https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbox
If you use Subclipse Plugin, you will need to accept the server certificate from the command line before you attempt to checkout anything with an SSL certificate. If you don’t accept the certificate permanently from the command-line, Subclipse will produce an error and fail.
My headshot is terrible, my writing is full of typos, and its my birthday.