Summary: | NPE inside qualified type reference resolution | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | David Audel <david_audel> |
Component: | Core | Assignee: | Kent Johnson <kent_johnson> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | eclipse-bug, eclipse-dev, rwk, siberski |
Version: | 3.0 | ||
Target Milestone: | 3.1 M2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
David Audel
2004-08-17 10:47:05 EDT
This is due to the reference changes. We no longer eagerly resolve the hierarchy of the type Y, so it doesn't know its interfaces when we look for Z. Actually I was wrong. This fails now (it doesn't fail in 3.0.1) because we added resolveSuperType(). We must detectCycles on each resolved type of the QualifiedTypeRef before resolving the next word. Reworked the resolveType of all TypeReferences to detect cycles. ClassScope.findSuperType now expects cycles to be detected in the call to resolveSuperType. See changes to GenericTypeTest.test112 *** Bug 73262 has been marked as a duplicate of this bug. *** *** Bug 73505 has been marked as a duplicate of this bug. *** *** Bug 69281 has been marked as a duplicate of this bug. *** *** Bug 73706 has been marked as a duplicate of this bug. *** *** Bug 73628 has been marked as a duplicate of this bug. *** Verified for 3.1 M2 with build I200409231635. |