Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361790

Summary: [changeset] Auto-Save for Team ChangeSets
Product: [Eclipse Project] Platform Reporter: Dominik Stadler <dominik.stadler>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: tomasz.zarna
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
Adds a simple Timer to the ChangeSetManager which saves the changeset every minute none

Description Dominik Stadler CLA 2011-10-24 05:59:57 EDT 
Build Identifier: 

I usually leave eclipse running for days only restarting it, when absolutely necessary. Sometimes Eclipse or the PC crashes for some unrelated reason, which means I am loosing all the ChangeSets that I defined in the Team Synchronize view.

Therefore I came up with the attached patch which automatically saves the ChangeSets every minute. 

I'm sure there are better ways to do this, this is just a quick way to solve my problem, comments about how this would look like for real are more than welcome!

Reproducible: Always

Steps to Reproduce:
1. Start Eclipse
2. Define some Changesets
3. Let Eclipse crash, e.g. kill the process

=> Changesets are gone

Bug 245977 and Bug 322618 are related, but not completely the same.
Comment 1 Dominik Stadler CLA 2011-10-24 06:00:46 EDT 
Created attachment 205793 [details]
Adds a simple Timer to the ChangeSetManager which saves the changeset every minute
Comment 2 Tomasz Zarna CLA 2011-10-24 06:08:25 EDT 
Wouldn't bug 98299 be a better solution for the problem?
Comment 3 Dominik Stadler CLA 2011-10-24 14:12:24 EDT 
Yes, solving Bug 98299 would make this one obsolete.
Comment 4 Lars Vogel CLA 2019-11-14 03:18:49 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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.