Bug 409369 - Uninstalling a feature do not remove related keybindings
Summary: Uninstalling a feature do not remove related keybindings
Status: CLOSED DUPLICATE of bug 406003
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-29 05:17 EDT by Raimar Bühmann CLA
Modified: 2013-07-04 12:53 EDT (History)
2 users (show)

See Also:

Attachments
Keybindings of an uninstalled feature still exist (33.12 KB, image/png)
2013-05-29 05:17 EDT, Raimar Bühmann CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Raimar Bühmann CLA 2013-05-29 05:17:44 EDT 
Created attachment 231692 [details]
Keybindings of an uninstalled feature still exist

Steps to reproduce:
1. install Eclipse Juno SR2
2. open installer via Help->"Install New Software..."
3. select "Juno - http://download.eclipse.org/releases/juno"
4. select a feature (e.g. Web Page Editor)
5. install and restart Eclipse
6. uninstall the previously installed feature and restart Eclipse
7. open the key bindings dialog via Window->Preferences->General->Keys

Current behavior:
The keyboard shortcuts of the uninstalled feature still exist.

Expected behavior:
The keyboard shortcuts of the uninstalled feature do not exist.

Hint:
The shortcuts are not removed from the file
workspace/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
by uninstalling its feature.
Comment 1 Curtis Windatt CLA 2013-05-29 09:54:08 EDT 
Isn't this the same as bug 406003?  All keybindings are stored in the xmi and are never cleared out.  Or do we plan on having special code to recognize a p2 operation?
Comment 2 Alexandra Schladebeck CLA 2013-05-30 02:52:27 EDT 
Thanks for the hint Curtis, looks like it is the same. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 406003 ***