Bug 89221 - [KeyBindings] errors: Keybinding errors logged when migrating a workspace
Summary: [KeyBindings] errors: Keybinding errors logged when migrating a workspace
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   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-28 10:35 EST by Randy Hudson CLA
Modified: 2019-09-06 15:33 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 Randy Hudson CLA 2005-03-28 10:35:52 EST
I get warning in the log (and most likely lost keybinding settings too) when
migrating my existing workspace to 3.1.

!SESSION 2005-03-28 10:34:05.73 ------------------------------------------------
eclipse.buildId=N20050325-0010
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments:  -application org.eclipse.ui.ide.workbench
Command-line arguments:  -application org.eclipse.ui.ide.workbench -debug

!ENTRY org.eclipse.ui 4 4 2005-03-28 10:34:05.73
!MESSAGE Warnings while parsing the key bindings from the preference store

!ENTRY org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Warnings while parsing the key bindings from the preference store
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration: commandId='null'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration:
commandId='org.eclipse.jdt.ui.edit.text.java.sort.members'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration:
commandId='org.eclipse.jdt.ui.edit.text.java.search.references.in.working.set'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration:
commandId='org.eclipse.jdt.ui.edit.text.java.format'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration:
commandId='org.eclipse.ui.window.nextEditor'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration:
commandId='org.eclipse.ui.edit.copy'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration: commandId='null'.
!SUBENTRY 1 org.eclipse.ui 2 0 2005-03-28 10:34:05.73
!MESSAGE Key bindings need a scheme or key configuration: commandId='null'.
Comment 1 Douglas Pollock CLA 2005-03-28 11:02:29 EST
Did you lose key binding settings?
Comment 2 Randy Hudson CLA 2005-03-28 11:35:57 EST
Yes, it seems I have lost some entries, but not many.  Also, I can't really say 
when they were lost since they aren't often used. It may have been R3.0 that 
lost the entries, but there were no log messages until 3.1.
Comment 3 Douglas Pollock CLA 2005-03-28 11:39:53 EST
Could you include the old preferences file (or, the current one, if it's all you
have)?  Also, which bindings are missing?
Comment 4 Randy Hudson CLA 2005-03-28 13:12:44 EST
Where are keybindings stored in 2.1, 3.0, etc?
Comment 5 Douglas Pollock CLA 2005-03-28 13:14:57 EST
In the "org.eclipse.ui.workbench" preference store.  For example, my 3.1
bindings are found in the following file:
   
"/home/dpollock/Source/Eclipse/Workspaces/3.1/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.workbench.prefs"
Comment 6 Michael Van Meekeren CLA 2006-04-21 13:14:15 EDT
Moving Dougs bugs
Comment 7 Paul Webster CLA 2006-09-28 15:14:34 EDT
Is this still a problem in 3.3?

PW
Comment 8 Denis Roy CLA 2007-06-22 09:32:50 EDT
Changes requested on bug 193523
Comment 9 Eclipse Webmaster CLA 2019-09-06 15:33:03 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.