Sep 13
One of our main reasons for switching to eclipse (and its CF plugin CFECLIPSE) was the excellent CVS (concurrent versioning system) integration.
It smooths out the kinks in CVS to make it an intuative tool to use.
For example if you move a file from one folder to another CVS wants you to delete and add very specifically, but eclipse just handles this for you in the background making it seem like a single commit operation.
All this power is available from the Navigation view (shows your projects and the files in them, in a tree structure) on the right click 'Team' menu. From here you can commit or update as appropriate.
One of the other Team options is the 'Synchronize' view
I tended to avoid this at first preferring to update and commit myself, however I'm now using this as my default view of the project from a CVS point of view. It gathers up incoming and outgoing changes that are pending and also highlights any conflicts (where you have edited a file and meanwhile another developer has commited a later version) and allows you to resolve those conflicts by displaying a diff of the two versions.
You can right click and update, commit, and resolve conflicts directly from this menu on individual files or on groups of files selected.
If you use CVS and CFECLIPSE give it a try.
It smooths out the kinks in CVS to make it an intuative tool to use.
For example if you move a file from one folder to another CVS wants you to delete and add very specifically, but eclipse just handles this for you in the background making it seem like a single commit operation.
All this power is available from the Navigation view (shows your projects and the files in them, in a tree structure) on the right click 'Team' menu. From here you can commit or update as appropriate.
One of the other Team options is the 'Synchronize' view
I tended to avoid this at first preferring to update and commit myself, however I'm now using this as my default view of the project from a CVS point of view. It gathers up incoming and outgoing changes that are pending and also highlights any conflicts (where you have edited a file and meanwhile another developer has commited a later version) and allows you to resolve those conflicts by displaying a diff of the two versions.
You can right click and update, commit, and resolve conflicts directly from this menu on individual files or on groups of files selected.
If you use CVS and CFECLIPSE give it a try.
Sep 14, 2006 at 6:27 AM Nice one bro.
Ever tried Subversion? What are your thoughts CSV vs Subversion?
Sep 14, 2006 at 9:53 AM Subversion vs. CVS. Well My view is that subversion is a newer product which has built on CVS and improved on some of its short-comings. So SVN is a better product. We started using CVS when SVN was not fully mature and so CVS seemed the better more solid bet. Using CVS through other tools can be more frustrating because the problems are more obvious (like moving files or renaming folders) but the eclipse implementation is so sweet that these issues never really bother us. SVN has atomic commits meaning that like a in a DBMS, transactions are managed and rolledback if a failure occurs anywhere. In theory with CVS if you commit ten files 9 might work and the tenth be dropped (due to a network failure for example). In practice however we have around 70 developers using our CVS repository from about 6 locations around the world 24/7 and have never had any serious problems. Probably if I was implementing source control from scratch now I would go with SVN as the better product, but CVS is a very solid alternative (and it does save you one extra eclipse plugin!)