[Javabdd-devel] Moving joeq/JavaBDD/bddbddb from CVS to Subversion
Brought to you by:
joewhaley
From: John W. <joe...@gm...> - 2006-06-07 20:11:12
|
Hello all, (I apologize in advance if you receive this email multiple times. I'm not sure how Sourceforge deals with sending to multiple mailing lists.) Now that Sourceforge has Subversion support, I'm planning to move the Java project repositories on Sourceforge from using CVS over to Subversion. Subversion is better that CVS in just about every possible way. First of all, actions on a repository are atomic. Second, it supports operations like renames and copies natively. Third, it does a much better job of working disconnected. Fourth, with Subversion there is no more lag between the anonymous and developer repositories. Fifth, it communicates using the standard https port rather than the ssh port, so it is more firewall-friendly. Sixth, the Eclipse Subversion plugin (Subclipse) appears to allow you to use both the command-line 'svn' command and the Subversion commands from the UI, whereas Eclipse CVS was incompatible with the command line 'cvs' command. And the list goes on and on... The downsides to switching over to Subversion are that everyone will have to check out a new copy of the source tree, the existing maven scripts for autogenerating the website will break, and you can no longer use it with Eclipse out of the box - you will need to install Subclipse. I've already ported over the repositories and I've tested out committing, Eclipse integration, etc. I've given SVN commit access to everyone who had CVS commit access. For the time being, the repositories are available from both CVS and Subversion. But at some point next week, I want to turn off CVS access and transition entirely to Subversion. Steps to moving over to Subversion: 1. If you are using Eclipse, install the Subclipse plugin by going to "Help -> Software Updates -> Find and Install", then clicking "Search for new features to install" and "Add new remote site". Add the site "http://subclipse.tigris.org/update_1.0.x" and continue, then select Subclipse to be installed. 2. If you are using cygwin, run the cygwin setup utility and install the subversion package. 3. Run CVS update on your existing checkout to update to the latest version and find any modifications you want to keep. 4. Check out a clean copy of the tree using Eclipse. Click on the "Open Perspective" button, then on "SVN Repository Exploring". Right click and add these repositories: https://svn.sourceforge.net/svnroot/bddbddb https://svn.sourceforge.net/svnroot/javabdd https://svn.sourceforge.net/svnroot/joeq Browse into the trunk directory of each repository and right-click to "Checkout..." the projects that you need. (If you have changes in the existing project you want to keep, you might want to move the project directory out of the way first.) You can also do it from the command line by using this command: svn co https://svn.sourceforge.net/svnroot/joeq/trunk joeq (Change 'joeq' to 'javabdd' or 'bddbddb' as necessary.) 5. Move any modified files you want to keep into the newly checked out tree, and commit them if necessary. Command-line subversion works much like command-line CVS. The major difference is to see what files you have modified, you can type "svn status" rather than "cvs update -Pd". If you could send an email when you've successfully made the transition, that would be great. -John |