Community
Participate
Working Groups
When shutting down, the workbench persists which views are open and where. When moving from release 2.X to 3.0, it may be possible that Views had their IDs renamed. For example, a view that was provided by Tool X, was pushed up into framework G. It is possible to update references in perspectives which used this view, but it isn't possible to update the persisted window state. To solve this problem, could Tool X provide a migration mapping in their plugin.xml? Stating that View xyz is now replaced by view abc? Otherwise, I think you get a popup dialog stating that a view could not be restored when restarting a workspace the first time. Perhaps this applies to things other than views, such as actionsets.
Investigate for R3.0.
I'm not an XSLT pro, but perhaps similar rules could be applied to morph one extension into another. We've encountered a similar situation where we want to migrate extension points from one plugin to another, e.g. for the RCP work.
The same could be done for extension points, etc.
ConsoleLog is an example of a view which was in 2.1, and has been renamed/moved in 3.0. As a result, my customized Java Perspective fails to come up and reverts to defaults.
deferring
There is currently no plan to work on this feature
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
