Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.15) Gecko/2009102815 Iceweasel/3.0.6 (Debian-3.0.6-3) Build Identifier: 20090920-1017 When Eclipse is started without the workspace being available (due to network fail or missed mounting), an empty workspace is generated and then saved when exiting Eclipse. If at the time of exiting the original workspace is suddenly present, Eclipse will override the existing workspace with an empty one (all projects have to be re-imported / configured). Request: automatically backup the project-settings related part of the workspace at startup. Allow recovering. Reproducible: Always Steps to Reproduce: 1. Disconnect workspace directory (i.e. unmount) 2. Start Eclipse 3. Reconnect workspace (mount) 4. Close Eclipse -> workspace lost
this happened with a truecrypt mount. It would be great to have some "restore-points" and a GUI in eclipse display the history of those and to revert to at least bigger of 5) the last 3 ones 6) the last 3 days
I am able to reproduce it. I would expect to see a warning saying that the workspace underneath was silently replaced. I think that the tree snapshot timestamp changes, so we could check it before a save.
I would have expected failures much earlier in startup if the workspace directory was on an unmounted drive...
(In reply to comment #3) > I would have expected failures much earlier in startup if the workspace > directory was on an unmounted drive... The issue is that you can mount a device to any folder at any time. You can choose a folder to be your workspace location and then a device can be mounted to this folder. My steps were: 1) I had a USB disc and 'workspace' folder in its root (workspace contained some projects already) 2) On Linux, I started Eclipse and choose '/media/WDPass/workspace' as my workspace folder (workspace was empty) 3) I mounted the disc to '/media/WDPass' 4) When Eclipse was closed, an empty tree was saved in the workspace on the USB disc
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.
