Bug 521890 - [9] Navigation fails on inherited static nested types from static import
Summary: [9] Navigation fails on inherited static nested types from static import
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-05 14:39 EDT by Jay Arthanareeswaran CLA
Modified: 2022-08-29 13:27 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 Jay Arthanareeswaran CLA 2017-09-05 14:39:08 EDT
Have the following classes in their own compilation units:

XYZ.java
------------
package a;
public class XYZ {
	public static class Inner {}
}


ABC.java
-------------
package a;
import static a.ABC.B.Inner;
public class ABC {
	static class B<Inner> extends XYZ {
		Inner in = null; // Code select works here
	}
}

Now navigating from the static import of a.ABC.B.Inner fails. Navigation also fails from the type parameter. However, it works when tried from the field declaration.
Comment 1 Manoj N Palat CLA 2018-05-21 06:13:49 EDT
Bulk move out of 4.8
Comment 2 Eclipse Genie CLA 2020-07-17 08:05:17 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 Eclipse Genie CLA 2022-08-29 13:27: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.