Community
Participate
Working Groups
JDT/Summit topic: Missing types can greatly deteriorate compiler output by producing too many secondary errors, surface suboptimal DOM bindings, or even abort entire compilation process when missing types are referenced from required classfiles. We should investigate ways to improve this situation, remembering that the APT Mirror API requires that bindings are still presented even in the presence of missing types.
First step is to consider improving the situation of missing types referenced (indirectly) from classfiles. These are causing abort compilation, and in certain situation will cause the global build process to fail altogether (see bug 114349).
Some progress was already made for local variables, see bug 144858
Also see bug 146768 for duplicate field/method issues
Also see bug 157996 for missing closest matches.
Also see bug 165662 for duplicate local types
To be investigated during M7
I just noticed this when doing a query of open plan item bugs... should this be added to the 3.3 plan? (http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html)
Removing "plan" keyword for now
Also see bug 179477 for array initializers.
Also see bug 166963 for misplaced explicit constructor calls
Closing. Most items got addressed. Few remaining ones are going to be left for later.
Verify for 3.3M7 with I20070503-1400.