Community
Participate
Working Groups
Change sets are currently persisted on shutdown. They should be persistd when they are modified to avoid losing them if Eclipse crashes.
+1
Upping severity since this causes data loss.
We'll try to address the issue in 3.6. However I don't see this is a major one. It is data loss prone but doesn't cause data loss by itself.
I recently had a situation where the current behavior even prevented data loss: I inadvertently closed all projects (bug 269844), and this trashed all my change sets (bug 76257). Fortunately, I remembered this bug and could thus manually save my precious change sets from the .metadata area. I now would only fix this bug when bug 76257 gets fixed as well...
*** Bug 322618 has been marked as a duplicate of this bug. ***
See also bug 361790.
Is this specific to the CVS component or should it be in the 'Team' component? I have the same issue with SVN. Still present in Luna R2 (4.4.2)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.