Bug 86942 - [Perspectives] Disabling a feature without closing the perspective causes error after restarting Eclipse
Summary: [Perspectives] Disabling a feature without closing the perspective causes err...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-01 15:37 EST by minyi CLA
Modified: 2019-09-06 15:29 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description minyi CLA 2005-03-01 15:37:36 EST
I have chosen Help component. Please reassign if this is not appropriate.

Our feature has a perspective. If I leave the perspective open and disable the
feature by using the Manage Configuration option under Help -> Software Updates
window, after I restart Eclipse, I get an error saying "Could not restore
workbench layout". The detail of the error says "Unable to restore perspective ...".

Eclipse should not try to restore the perspective/views if the feature has been
disabled.
Comment 1 Dejan Glozic CLA 2005-03-01 15:38:52 EST
This is Update.
Comment 2 Dorian Birsan CLA 2005-03-01 15:46:27 EST
Moving to UI for comments.

What happens here is that on eclipse restart, the plugins associated with the 
disabled feature are uninstalled from the runtime.
At this point, update does not know anything about perspectives and such. On a 
first thought, it looks like the UI component should handle this in a non-
disruptive way.
Comment 3 Nick Edgar CLA 2005-03-07 14:24:51 EST
If a perspective is missing on restore, we could just skip it, and continue
silently.  If no perspectives could be restored, we would just open a default
window.  Need to ensure that any ref counts for views shared across perspectives
are fixed up accordingly.
Comment 4 Nick Edgar CLA 2006-03-15 11:46:52 EST
Reassigning bugs in component areas that are changing ownership.
Comment 5 Paul Webster CLA 2006-09-28 15:14:29 EDT
Is this still a problem in 3.3?

PW
Comment 6 Denis Roy CLA 2007-06-22 09:32:49 EDT
Changes requested on bug 193523
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:29:41 EDT
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.