Community
Participate
Working Groups
Between major product adopter releases, the format of workspace metadata might change. Builders may no longer apply. Classpath containers might have been renamed or become obsolete. Project preference keys may have been renamed, or the format changed. WTP Facets might need to be altered. There needs to be to run code to "upgrade" the old workspace into a current format. Ideally, this needs to run right after the workspace itself is opened. It should lock the workspace, so nobody else can write to it. Builders should be suspended during this time. It needs to be able to access the UI to present a preview of the changes that will be performed to the user for approval. (The main workbench window does not NEED to be showing - all interaction should be done in the modal UI dialog - perhaps this can be combined with the "choose workspace" dialog that appears on Eclipse startup?) All other Eclipse API calls should succeed. (Reading project preferences/resolving/setting a classpath, etc.)
I thought Eclipse works already that way. I mean every component is responsible for keeping backward compatibility...
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.
