Bug 458135 - There is no handler to execute for command *refactor command*
Summary: There is no handler to execute for command *refactor command*
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.4.1   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2015-01-22 08:18 EST by Alan Schelten CLA
Modified: 2020-07-01 16:04 EDT (History)
1 user (show)

See Also:


Attachments
Error Log for described problem. (3.09 KB, application/octet-stream)
2015-01-22 08:18 EST, Alan Schelten CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Schelten CLA 2015-01-22 08:18:14 EST
Created attachment 250140 [details]
Error Log for described problem.

I'm getting the error log attached quite often, when attempting to trigger a java refactoring operation using quick assist in the editor window. Eclipse changes focus to a different view and gives an error message.
Comment 1 Dani Megert CLA 2015-01-26 04:56:04 EST
Are you sure you're on 4.4.1?
Are there other entries in the .log, e.g. handler conflicts?


Internal note: Similar bug is supposed to be fixed in 4.4: bug 433778.
Comment 2 Alan Schelten CLA 2015-01-27 04:22:56 EST
The problem only persists if the toolbar is toggled to be invisible. You then get a different style of quick access, (not quick assist, sorry for the error in the original post) with a yellow background at the center of the screen.
The log entry in the attachement is the only one I get.
Version is:
Eclipse SDK

Version: Luna SR1 (4.4.1)
Build id: M20140925-0400
Comment 3 Eclipse Genie CLA 2020-07-01 16:04:40 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.