Bug 515597 - Generalize Declared Type refactoring seems to ignore method references
Summary: Generalize Declared Type refactoring seems to ignore method references
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2017-04-21 14:49 EDT by Raffi Khatchadourian CLA
Modified: 2023-05-09 18:41 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raffi Khatchadourian CLA 2017-04-21 14:49:34 EDT
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.
Comment 1 Eclipse Genie CLA 2020-08-16 14:02:28 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.
Comment 2 Kalyan Prasad Tatavarthi CLA 2020-08-17 02:39:30 EDT
(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.
Comment 3 Eclipse Genie CLA 2023-05-09 18:41:14 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.