Bug 548904

Summary: Spurious find references potential matches
Product: [Eclipse Project] JDT Reporter: Ed Willink <ed>
Component: UIAssignee: JDT-UI-Inbox <jdt-ui-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3    
Version: 4.13   
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard:
Attachments:
Description Flags
Screenshot none

Description Ed Willink CLA 2019-07-03 05:38:06 EDT
Created attachment 279163 [details]
Screenshot

While searching for 

org.eclipse.uml2.uml.resources.util.init(ResourceSet resourceSet)

which is a static method, the search finds the non-static

org.eclipse.debug.internal.ui.commands.actions.ToggleStepFiltersAction.init(IWorkbenchPart part)

as a potential match. See screenshot attached. How???

static/non-static are incompatible.

ResourceSet and IWorkbenchPart have only Object in common.

(Perhaps this is a repro of a general inability of searches for e.g. INSTANCE to be pruned to credible options.)
Comment 1 Ed Willink CLA 2019-07-03 05:51:44 EDT
After a bit of a play, I discovered a "Potential Matches" menu option.

Once selected and deselected a few times, it appears to have inverse polarity. When tick-Potential Matches is displayed no potential matches are shown.

The menu gives no cue as to the actual polarity. Is "In Imports" a filter to enable/suppress functionality "In Imports".

The initial state is more consistent, so perhaps the problem is that whenever this filtering option was introduced the default fails to correlate with the preference or the default preference was mis-defined.
Comment 2 Eclipse Genie CLA 2021-06-23 09:36: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 2023-06-14 05:00:36 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 4 Ed Willink CLA 2023-06-14 05:07:05 EDT
Cannot be stale till triaged by a relevant committer.