Summary: | Search for constructor references occasionally wrongly reports type constructors when type has other matching methods | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Brian de Alwis <bsd> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.2 M2 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: |
Description
Brian de Alwis
2005-09-12 21:35:38 EDT
Unfortunately, there's nothing search engine can do in this case. The reported invalid matches are super references which can be filtered by search engine as there's no binding on compilation unit of Java search path plugins (see bug 83716 comment 7 and bug 83716 comment 9 for details). We currently prefer reporting those invalid matches than miss some real potential ones... Of course, in previous comment you should read: The reported invalid matches are super references which CANNOT be filtered by search engine... |