I just wish there was an easier way to test the changesets independently. Currently I test ALL my changes locally, then check in a changeset and depend on an automated build server to tell me if I missed something.

Usually the local testing works, but there have been cases where there was subtle dependencies between my changesets and the build on the build server failed. Of course in those cases I do analysis and fix the problem. But firstly, not everybody has automated build servers. And secondly, it would be nice to be able to test before committing so you do not break the build.

Another thing I forgot to mention is that if you choose to commit an entire change set through the “synchronize” view then eclipse seems to decide that you’re done with the change set and it disappears.

Unfortunately, I haven’t had time to look into where the change set information is stored, or what all the different actions might be that could remove change sets.

If you think the idea behind change sets seems like it would be helpful but you want more flexibility, then you might want to look into a more full-featured plugin such as Mylar (http://www.eclipse.org/mylar/).

Where is the change set information stored? What actions can potentially remove them? In my case, I often close and re-open projects within the workspace..