Summary: | search: java project scope does not work as expected (1GIJU1P) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M1 | ||
Hardware: | All | ||
OS: | Windows NT | ||
Whiteboard: | |||
Bug Depends on: | |||
Bug Blocks: | 3895 |
Description
Jerome Lanneluc
2001-10-10 22:53:29 EDT
Wondering if the workbench scope issue is not rather related to ignoring the fact that some matches are inacurrate. Last scenario just seems like a bug. If going for extra flags, this would only be helper methods (include prerequisites and/or include dependents). Workspace scope issue is due to the fact that bindings don't know where they're coming from. So there is no way to distinguish between a junit.framework.TestCase coming from JUnit and junit.framework.TestCase coming from JUnit1. This is the same problem for last scenario. The only way to solve this is to do what Adam suggested: add a flag that indicates if referenced projects should be included. Added SearchEngine.createJavaSearchScope(IJavaElement[] elements, boolean includeReferencedProjects). PRODUCT VERSION: 0.9 |