Bug 98299 - [Change Sets] Change sets should be persisted when they are changed
Summary: [Change Sets] Change sets should be persisted when they are changed
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 normal with 4 votes (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
: 322618 (view as bug list)
Depends on: 76257
Blocks:
  Show dependency tree
 
Reported: 2005-06-03 11:10 EDT by Michael Valenta CLA
Modified: 2019-12-24 06:26 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2005-06-03 11:10:54 EDT
Change sets are currently persisted on shutdown. They should be persistd when 
they are modified to avoid losing them if Eclipse crashes.
Comment 1 Markus Keller CLA 2007-06-18 05:27:13 EDT
+1
Comment 2 Markus Keller CLA 2007-12-04 08:04:02 EST
Upping severity since this causes data loss.
Comment 3 Pawel Pogorzelski CLA 2009-05-08 06:29:23 EDT
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.
Comment 4 Markus Keller CLA 2009-05-08 06:46:21 EDT
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...
Comment 5 Dominik Stadler CLA 2011-10-24 14:11:00 EDT
*** Bug 322618 has been marked as a duplicate of this bug. ***
Comment 6 Tomasz Zarna CLA 2011-10-25 04:32:49 EDT
See also bug 361790.
Comment 7 Vince Mising name CLA 2015-12-23 17:58:24 EST
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)
Comment 8 Eclipse Genie CLA 2019-12-24 06:26:38 EST
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.