| Summary: | ResourcesPlugin bundle start fails on missing launch configurations | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andreas Goetz <cpuidle> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, sptaszkiewicz |
| Version: | 3.6.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Andreas Goetz
Duplicate of bug 149121. See bug 149121 comment 50 on how to recover manually your workspace. *** This bug has been marked as a duplicate of bug 149121 *** The cause of ObjectNotFoundException is different than in bug 149121. Reopening. There is a workspace available in bug 149121 comment 69 that shows that problem. The problem is that .snap file is very old (2009-06-06) and does not match the date of tree file (2011-03-25). Old .snap is no longer applicable over latest tree file since it is a snapshot for some previous version of tree file. Normally, .snap file is deleted after FULL_SAVE (e.g. on Eclipse shut down) so this is very strange how it is possible that the file is still there after almost 2 years. Andreas, are you able to tell us what happened to that workspace since 2009? To recover your workspace, please delete .snap file. It was created in 2009 as a temporary save file and since then there were a few full saves performed, so .snap is no longer adequate for your workspace. Deleting the .snap file resolved the problem. Unfortunately- as the workspace was migrated from a now scrapped machine- I'm unable to identify the cause of the outdated .snap file. I'm suggesting closing this bug again. (In reply to comment #4) > Deleting the .snap file resolved the problem. Unfortunately- as the workspace > was migrated from a now scrapped machine- I'm unable to identify the cause of > the outdated .snap file. I'm suggesting closing this bug again. Thanks for this feedback, I am glad your problem is resolved. I am closing this bug as requested. |