Summary: | NPE in SearchEngine when matching type against ProblemReferenceBinding | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Artem Tikhomirov <tikhomirov.artem> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | minor | ||||||
Priority: | P3 | ||||||
Version: | 2.0.2 | ||||||
Target Milestone: | 3.0 M1 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Artem Tikhomirov
2003-05-02 08:05:33 EDT
Created attachment 4774 [details]
JUnit test case
Initial description is a bit wrong - only first deleted cu (cu1) should be
explicitly imported into cu3. And names of the CUs should be simmilar (only
suffixes differ). cu1 and cu2 are referenced by their fq names.
Before running this testcase, you need a java project (project as a source
root)named "SearchEngineBindingProblemTest" in your workspace. If I create it
from setUp, it has some problems with classpath, so
MatchingOpenable.shouldResolve became false (MatchLocator gets
AbortCompilation), so no attempt to resolve reference done.
A lot of changes occured in this area in 2.1. Could you please try with Eclipse 2.1 and see if you still have the problem? Yes, it is reproducable in 2.1. Hope, next comment won't be "please suggest a fix". I consider testcase is pretty good contribution from my side. Thanks a lot for your test case. Fixed TypeDeclarationPattern.matchLevelForType(...) to handle ProblemReferenceBindings. Added regression test JavaSearchTests.testTypeOccurence2() Verified. |