On Friday 24 February 2006 06:30, Martijn Dashorst wrote: > As for subversion/cvs there are apparently pro's and cons. According > to sourceforge SVN is slower than CVS, so that might be a downside. I > have no data to confirm this claim.
I don't have numbers, but quite a lot of experience. First off; Apache Software Foundation is probably a "showcase" installation, but as of 1 Jan 2006, CVS write access has been disabled and all projects have migrated to SVN. The general impression across hundreds of developers are predominantly positive. Pros (my view); * Atomic commits. All files are committed in a single operation, or the operation will fail. * Move. You can move things around without the CVS-styled penalties. * Local Revert. Subversion actually keeps the checked-out code in parallel, so if you want to revert the local changes it is very fast, and no need to delete and update from server. * Defaults to binary type. Typically, you set up your system that the common file types are text. * Proper End-Of-Line handling. You can tell it that *.bat files must have CRLF, *.sh must have LF and *.java should follow the OS on the local system. * Many useful metadata tags, such as svn:ignore, svn:external. * IDEA support is very good. Full refactoring support, and I have not observed any strange behaviour, even though I have messed around heavily with a mid-sized application for a long time. Cons; * It happens that the local system gets messed up (just like on CVS), but unlike CVS one typically doesn't have a chance to restore it by manipulating the management files. * Some of the serverside operations seems slower. * The server crashes. ASF has experienced this in the past, but I don't know why it happened. Personally, I am experiencing that the Apache server crashes. No data is ever lost, just annoying that it has to be restarted, and in case of ASF it could take a couple of hours before a "root person" was available to restart it. * Eclipse support is VERY POOR. Don't expect that any refactoring will work, and expect that files occassionally are missing. Apparently, this is the case for CVS as well, but since people doesn't move stuff around in CVS as much, it is less obvious. Someone told me that it is due to a weak underlying model in Eclipse. > I believe that Netbeans still has to build in SVN support, and > subclipse is external to the eclipse project, so it will be behind in > features and ease of use when compared to the CVS support. I can't speak for Netbeans, as I have no experience. > I will perform a test import of our CVS repository to see how this > works out. Later on, when we decided whether or not to move to SVN, I > will take a moment and perform the import once again but with more > recent data. If you want Import help, I think people at ASF could lend you a hand and provide some tips. After all, a handful of peeps there have imported ~180 projects, over a period of ~2 years. If you are not managing the server, I don't think the cons are very strong, and it is likely that you will not regret the decision. I hope this help you decide. Cheers Niclas ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
