I haven't followed every bit of the thread on the SVN migration, but I just want to echo Martin Cooper's sentiments: once you start using it, you realize how badly CVS was in need of an overhaul. For Struts, not only have there been no committers who have mentioned any significant problems in switching, but as Martin noted, we've been able to do a lot to clean up the repository. (Admittedly something which may be less necessary for Commons projects.) The most notable incident I personally experienced was about half-an-hour's research and experimentation to understand the differences in how SVN does keyword substitution.

The SVN command-line client is easy to use and far better documented than CVS (http://svnbook.red-bean.com/svnbook-1.1/index.html), and I've recently been played around with Subclipse for Eclipse, and it seems to be about what you'd need in terms of IDE integration. Don't know about IDE level support for other tools, but Windows users also speak well of Tortoise SVN.

I'm still trying to figure out how to get a convenient list of what tags have been applied to a file (and which version they are) comparable to the beginning of a 'cvs log' command, and similar functionality seems to not yet be in viewcvs for SVN repositories -- but that hasn't been a major issue.

I am definitely +1 on migrating to SVN.

Joe

--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction"  -The Ex

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to