My team is currently looking at upgrading our version control software. Right now we are using an outdated version of Starteam - 4.1. While we are considering upgrading to the current version of Starteam, we are also looking at other options. One we are considering is CVS. It obviously has several positives - commonly used, stable, lots of documentation, good tool support. However, from my past experience with CVS, I remember it being cumbersome/impossible to move/rename a file while maintaining its history. I also remember it being impossible to remove a directory. My question is this - does using CVS hinder aggressive refactoring? If you are constantly moving, renaming, consolodating files, does CVS create a problem with this? If not, how have you overcome this? Thanks. Ryan
Hello Ryan, welcome to JavaRanch. That's an interesting question. It would be interesting to see how the Eclipse IDE (using CVS) handles the renaming of a class, which means that its containing file would have to change its name and the CVS repository would have to be updated.
If you rename/move a file, CVS will loose its history. Eclipse can't change this behaviour. You should take a look at SubVersion, which is known to handle those things much better.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
posted 15 years ago
Originally posted by Ilja Preuss: If you rename/move a file, CVS will loose its history. Eclipse can't change this behaviour. You should take a look at SubVersion, which is known to handle those things much better.
I have been looking a SubVersion this monring. Getting it installed is a nightmare. I am having no luck and their docs aren't very clear. Have had success with this?