Bug 271385 - Navigating to inner class goes to wrong class when there are multiple inner classes of the same name in a binary type
Summary: Navigating to inner class goes to wrong class when there are multiple inner c...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2009-04-06 18:24 EDT by Andrew Eisenberg CLA
Modified: 2023-01-02 00:19 EST (History)
2 users (show)

See Also:


Attachments
project that exhibits this problem (4.60 KB, application/octet-stream)
2009-04-06 18:27 EDT, Andrew Eisenberg CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Eisenberg CLA 2009-04-06 18:24:29 EDT
This bug is best described by the project I am going to attach.
Comment 1 Andrew Eisenberg CLA 2009-04-06 18:27:26 EDT
Created attachment 131066 [details]
project that exhibits this problem

Navigation to G.Inner goes to G.Inner3.Inner instead.

Steps to reproduce:

1. import project
2. ensure full build
3. put caret on the 'Inner' part of G.Inner
4. press F3
5. navigation goes to G.Inner3.Inner instead of G.Inner
Comment 2 Dani Megert CLA 2009-04-07 03:50:37 EDT
Code resolve works correctly but org.eclipse.jdt.core.ISourceReference.getSourceRange() is wrong.
Comment 3 Dani Megert CLA 2009-04-07 05:37:06 EDT
See also bug 137847.
Comment 4 Andrew Eisenberg CLA 2009-04-20 12:31:11 EDT
Any hints here?  I have some experience with JDT and can submit a patch.
Comment 5 Olivier Thomann CLA 2009-12-14 14:25:08 EST
I'll take a look.
Andrew, feel free to provide a patch. I'll review it as soon as it is available.
Comment 6 Eclipse Genie CLA 2020-09-27 15:51:55 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 7 Eclipse Genie CLA 2023-01-02 00:19:11 EST
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.