Summary: | NPE in Engine if type collides with a package | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Stephan Herrmann <stephan.herrmann> | ||||
Component: | Core | Assignee: | David Audel <david_audel> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.4.1 | ||||||
Target Milestone: | 3.5 M3 | ||||||
Hardware: | Other | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Stephan Herrmann
2008-09-29 15:29:18 EDT
If you want to see more delete the package declaration in C2: java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.problem.ProblemReporter.packageCollidesWithType(ProblemReporter.java:5414) at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.buildTypeBindings(CompilationUnitScope.java:87) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.buildTypeBindings(LookupEnvironment.java:147) (this NPE is actually somewhat obtrusive ..) The same problem would also occur (I guess) if mustSpecifyPackage is reported. I wasn't, however, able to easily trigger that error. (Is it actually raised?) The bug descibed in comment 1 is not the same as bug described in comment 0. I filed a new bug report for problem 2 (bug 251690). Created attachment 115805 [details]
Proposed fix
Released for 3.5M3 Tests added ResolveTests2#testBug249027a() -> testBug249027b() Verified for 3.5M3 using I20081026-2000 |