Summary: | Generalize Declared Type refactoring seems to ignore method references | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Raffi Khatchadourian <raffi.khatchadourian> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | kalyan_prasad, raffi.khatchadourian |
Version: | 4.7 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: | stalebug |
Description
Raffi Khatchadourian
2017-04-21 14:49:34 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. -- The automated Eclipse Genie. (In reply to Raffi Khatchadourian from comment #0) > Issuing a Generalize Declared Type refactoring results in a possible > compilation error in the context of method references. In other words, the > refactoring doesn't seem to consider method references in its analysis of > the type. Please provide a sample example to demonstrate the above issue. 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. -- The automated Eclipse Genie. |