Bug 39062 - Too many matches found querying method declarations with wild cards
Summary: Too many matches found querying method declarations with wild cards
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M4   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-18 07:48 EDT by Jerome Lanneluc CLA
Modified: 2003-10-06 04:36 EDT (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 Jerome Lanneluc CLA 2003-06-18 07:48:56 EDT 
Build 20030611

Too many matches are found searching in jdt.core for method declarations with 
the following pattern:
'org.eclipse.jdt.core*.* boolean'

For instance, it finds:
org.eclipse.jdt.internal.compiler.problem.DefaultProblem.isError()
which is in org.eclipse.jdt.internal.compiler.problem (and not 
in 'org.eclipse.jdt.core*)
Comment 1 Kent Johnson CLA 2003-10-01 14:40:31 EDT 
The problem is that this type 
org.eclipse.jdt.internal.compiler.problem.DefaultProblem inherits from the 
interface org.eclipse.jdt.core.compiler.IProblem.

So what it comes down to is when you search for method declarations of the 
method p1.I.foo(), should you find p2.B.foo(), because B implements the 
interface p1.I?
Comment 2 Jerome Lanneluc CLA 2003-10-02 04:53:50 EDT 
Agreed, we should also find p2.B.foo(). 
This bug is invalid. Please close.
Comment 3 Kent Johnson CLA 2003-10-02 10:47:43 EDT 
Not a bug.