Bugzilla – Full Text Bug Listing
| Summary: | [Search][Javadoc] Search for method with boolean argument returns wrong matches | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Gary Gregory <ggregory> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel_megert |
| Version: | 3.0 | ||
| Target Milestone: | 3.1 M1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Those might be so called potential matches (see Window > Preferences > Workbench
> Search). Do they have (inexact) or (potential) in the name?
Do you have compile errors in those types?
Dani was right here. Please set ON compiler option "Malformed Javadoc Comments" (in Javadoc tab) and then you should see that the reference in @see tag is not resolved... If you fix this error, then you should not find this reference again. You can also ignore potential matches by checking Workbench->Search->"Ignore potential matches" preference. And then, even without fixing your unresolved reference, you won't have this unexpected search result... Close as not comment was made on proposed options activation. |
Version 3.1.M1. I have a method defined "LogTarget process(boolean b)" in a class A in package P1. In the Java Browsing Perspective, in the Members pane, I right-click/References/Workspace and get incorrect references in all different packages and classes in my workspace. Calls to the method are correctly matched but extra matches are also returned in the Search View. For example, the following "process" reference is matched in all Javadocs: /** * Do the actual processing of the action. * * @see com.seagullsw.appinterface.tools.securitytoolkit.action.Action#process(ActionCommandLineSettings) * * @param actionCommandLineSettings the pre-processed command line arguments for this action. */ The class in the @see is "com.seagullsw.appinterface.tools.securitytoolkit.action.Action" which is NOT "A". I have many such mismatches which makes the Search feature not much better than a plain text search on "process".