Summary: | Java Search for OR-pattern finds too much in strange project setup | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> | ||||
Component: | Core | Assignee: | Kent Johnson <kent_johnson> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 2.1.2 | ||||||
Target Milestone: | 3.0 M8 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Markus Keller
2003-12-10 14:43:35 EST
Created attachment 7107 [details]
3 projects for workspace
Marcus: is this a 2.1.x problem only? Or does it also happen in the 3.0 stream? If its just a 2.1.x problem then we likely won't fix it. Hi Cent ;-) It's also a 3.0 "problem" (I don't think it's too severe): To look at it, - set up the zipped workspace in a run-time eclipse - set a breakpoint in RenamePackageProcessor#getReferencesToTypesInNamesakes(..), in the third-to-last line (before ... RefactoringSearchEngine.search(..) ...). - select package p from projectA - Refactor > Rename... to "asdf", with updating references to the renamed element - click 'Preview >' - when you hit the breakpoint, step into the search, and soon you'll hit familiar jdt-core land ;-) The problem was with the TypeReferencePattern. It didn't consult with the supplied focus. I cannot reproduce in 3.0 M7. Kent which build did you use to reproduce it? Not sure exactly but I suspect it was M7 (or an integration build shortly after). Kent can you please verify the bug is fixed in latest integration build? |