Summary: | A blocking "java.lang.IllegalArgumentException: info cannot be null" exception | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Tomasz Zarna <tomasz.zarna> | ||||||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||||
Severity: | major | ||||||||||
Priority: | P3 | CC: | amj87.iitr, Olivier_Thomann | ||||||||
Version: | 3.7 | ||||||||||
Target Milestone: | 3.7 M3 | ||||||||||
Hardware: | PC | ||||||||||
OS: | Windows XP | ||||||||||
Whiteboard: | |||||||||||
Attachments: |
|
Description
Tomasz Zarna
2010-09-17 06:51:46 EDT
Created attachment 179100 [details]
The problematic project exported to zip file
Once I've fixed the errors in the code, without any assistance from JDT and ignoring hordes of exceptions in the error log, the JDT seems to be back to normal. Lowering priority. I'll take care of this. The fix for bug 324848 exposes an existing bug. In your case the variable before and after may have not been initialized when used inside the anonymous type. We now properly report the problem against the anonymous type method declaration instead of flagging the outer method. The problem with that is that the code generation for the outer method cannot be done because the variable might not be initialized. In order to generate the anonymous type instantiation, the value of the local variable before is required, but at that moment it might not be initialized. I am working on a fix for M3. Created attachment 179141 [details]
Proposed fix + regression tests
Patch under test
Created attachment 179145 [details]
Proposed fix + regression tests
Released patch (same patch with minor test changes)
Released for 3.7M3. Regression tests added in: org.eclipse.jdt.core.tests.compiler.regression.ProblemTypeAndMethodTest#test113 org.eclipse.jdt.core.tests.compiler.regression.InitializationTests#test325567 Verified for 3.7M3 using build I20101025-0901. |