Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 425407

Summary: [search] for references to fields {typename}.* finds tons of wrong potential matches
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: CoreAssignee: Manoj N Palat <manoj.palat>
Status: CLOSED MOVED QA Contact:
Severity: normal    
Priority: P3 CC: manoj.palat, simeon.danailov.andreev
Version: 4.4   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Markus Keller CLA 2014-01-10 09:42:36 EST 
master, BETA_JAVA8, at least back to 3.6.2. Could be a variant of bug 423409.

A search for references to fields {typename}.* finds tons of wrong potential matches:

- Import > Plug-ins and Fragments > Binary projects:
    Choose org.eclipse.jdt.core and org.eclipse.core.commands

- Search > Java...:
    For "org.eclipse.jdt.core.dom.QualifiedName.*", Fields, References, Workspace

=> Finds completely inexplicable potential matches like "@see #describe" in org.eclipse.core.runtime.content.IContentDescriber#getSupportedOptions()

This also happens if everything is in source.
Comment 1 Eclipse Genie CLA 2020-09-03 19:07:22 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 Eclipse Genie CLA 2022-09-01 15:25:35 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 Simeon Andreev CLA 2023-03-17 17:05:48 EDT 
Opened: https://github.com/eclipse-jdt/eclipse.jdt.core/issues/861