Bug 534565 - [open type] Cannot find inner class of anonymous class
Summary: [open type] Cannot find inner class of anonymous class
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact: Manoj N Palat CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-11 04:21 EDT by Lukas Eder CLA
Modified: 2022-09-01 05:05 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Eder CLA 2018-05-11 04:21:22 EDT
Consider this code:

----------------------------------------
public class Inner {
    Object o = new Object() {
        class FindMe {}

        {
            new FindMe();
        }
    };
}
----------------------------------------

The FindMe type cannot be found using the Open Type dialog
Comment 1 Jay Arthanareeswaran CLA 2018-05-11 06:00:42 EDT
I quickly checked to see if this is a recent regression but I can see this behavior as far back as 4.5.2.

Manoj, can you please check.
Comment 2 Eclipse Genie CLA 2020-05-25 02:23:51 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 3 Lukas Eder CLA 2020-05-25 02:56:46 EDT
This is still a problem
Comment 4 Eclipse Genie CLA 2022-09-01 05:05:12 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.