Bug 5527 - Unexpected inaccurate matches for #close() declarations
Summary: Unexpected inaccurate matches for #close() declarations
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P2 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-05 09:06 EST by Philipe Mulet CLA
Modified: 2002-01-11 09:13 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2001-11-05 09:06:32 EST 
Build 207 + patch JDTCORE (including null check for 5526)

STEPS:
- Take same workspace as for 5526 (n:/archive/workspaces/5526.zip)
- When searching declarations of a method named 'close' through Java search 
page, some inaccurate matches are displayed in the list, which should be 
accurate matches:

e.g.

?: org.eclipse.jdt.debug/src - 
org.eclipse.jdi.internal.connect.TransportImpl.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.dialogs.OpenTypeSelectionDialog.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.jarpackager.JarPackageReader.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.jarpackager.JarPackageWriter.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.text.JavaCodeReader.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.text.javadoc.JavaDocCommentReader.close()
?: org.eclipse.jdt.ui/src - 
org.eclipse.jdt.internal.ui.text.SubstitutionTextReader.close()
?: org.eclipse.search/src - 
org.eclipse.search.internal.workingsets.WorkingSetReader.close()
?: org.eclipse.search/src - 
org.eclipse.search.internal.workingsets.WorkingSetWriter.close()
Comment 1 Philipe Mulet CLA 2001-11-06 09:18:10 EST 
In this scenario, I do not get why any resolution would even be needed...
Comment 2 Jerome Lanneluc CLA 2001-11-06 11:59:49 EST 
You are right. The matchLevel(...) methods didn't take the needsResolve flag 
into account.
Fixed (but not yet released)
Comment 3 Jerome Lanneluc CLA 2001-11-06 12:51:07 EST 
Released.