Bug 54435 - Very imprecixe results from reference search
Summary: Very imprecixe results from reference search
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-11 05:02 EST by Martin Aeschlimann CLA
Modified: 2004-04-22 11:44 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Aeschlimann CLA 2004-03-11 05:02:20 EST
20040311

In a selfhosting workspace (all binary except e.g. jdt.ui) open
'SelectionDialog.getMessage'

Search for references:
you get results like
e.getMessage where e in an exception, or IXMLAnnotation.getMessage

I turned off 'ignore inexact matches', but that didn't help
Comment 1 Olivier Thomann CLA 2004-03-24 11:41:07 EST
I think this is a consequence of using external jars. The type reference might
not be resolvable. Therefore more inexact matches are returned.
Comment 2 Jerome Lanneluc CLA 2004-04-05 08:32:26 EDT
Martin, are you using PDE's 'External Plug-in Libraries' project?
Comment 3 Martin Aeschlimann CLA 2004-04-05 09:03:17 EDT
no external plugins.
it's a (standard) self containing workspace (no links), with source and binary 
plugins
Comment 4 Jerome Lanneluc CLA 2004-04-05 12:20:07 EDT
New search view doesn't take accuracy into account. If I use the old search 
view, the 'e.getMessage()' matches are shown as inexact.
Comment 5 Jerome Lanneluc CLA 2004-04-05 12:34:04 EDT
All inexact matches I get are coming from osgi plugin that is obviously missing 
some jars. Martin can you still reproduce in latest integration build? If you 
can, I would need more details on how to reproduce this problem.
Comment 6 Jerome Lanneluc CLA 2004-04-22 11:44:51 EDT
Please reopen if you have more details.