Using CVS change sets
It seems to be a little known fact that the Eclipse CVS integration supports CVS change sets. Now, what is this? Have a look at the following figure:
What we see here is a typical situation: you have been working on a new feature in your local workspace while your teammates weren’t lazy either and have been hacking away some code. The synchronize view gives you an impression of which changes are outgoing ones and which ones are incoming ones.
However, there are several problems with this view. First, you cannot see which changes belong to each other. You also cannot see who has been performing the changes. And last, you cannot see why the changes have been made.
All these shortcomings can be overcome by using CVS change sets. The same situation with change sets activated looks like this:
Now you can easily see who has been changing what for which reason.
Here’s how to use change sets:
- Make sure that change set models are activated in the synchronisation preference dialog:
- Activate the changeset model in the sychronize view models dropdown menu:
- Last, but not least: make sure you and your teammates use commit comments! It is a good habit to comment each and every commit. For CVS change sets to be useful, you should NOT use a different commit comment for each single file, but rather use one comment for all files that belong to a logical change (e.g. a bug fix).
Give it a try. I am sure you won’t look back.
Thanks for reading this post. Follow me on twitter here to be notified about updates and other posts I write. Or, subscribe to my RSS feed here. If you want to get in touch with me, use the contact form.