Community
Participate
Working Groups
Build Identifier: As option, backup the current workspace before starting the workbench. The loss of a workspace means the loss of all settings and customizations made within this workspace. Without a current backup, in the best case, possibly a lot of time to recreate the workspace settings; in the worst case, irreparable loss of work. This is a major issue when work spaces become corrupted. If a backup was available, it could be restored. Reproducible: Sometimes Steps to Reproduce: See Details
Can you be more specific, please? The question is whether you'd want the full workspace to be backed up (including all your projects)? Or maybe just the workspace-specific metadata, i.e. the information that plug-ins store in the .metadata directory within the workspace directory (this would include things like workspace-wide compiler options etc)? Or is it just about backing up the workbench settings such as which keybindings, views, color settings etc.?
I think a backup is best accomplished with a client script before launching the application. The application doesn't know the workspace location until after the workspace prompt appears. From that point, various parts of the metadata may be locked or under modification so there is no safe time to do a complete backup of workspace content and metadata. However, this feels like a band-aid solution to a problem of frequent workspace corruption. The workspace should never become corrupt, so if this is happening to you on a regular basis we would like to narrow down what might be causing that.
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.
