Community
Participate
Working Groups
We've recently upgraded our Java null annotations from "eclipse-jdt-annotations-1.1.0.jar" (declaration-based) to "eclipse-jdt-annotations-2.2.4.jar" (type-based). Previously Eclipse's incremental compilation worked well for our projects containing over 8000 files, but after the upgrade even small changes trigger a full rebuild of the our code. This includes changes to comments. Switching back to the old annotations resolves the problem. We can't tell if disabling the null analysis would help as if we go Window -> Preferences -> Errors/Warnings and uncheck "Enable annotation-based null analysis", then Eclipse throws the following NPE when we then rebuild the project: Internal compiler error: java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.constantPoolName(TypeVariableBinding.java:410) Graph.java /Utilities/src/java/com/dugeo/lib/math line 0 Java Problem Creating a new workspace and reimporting the projects also does not help.
Please do two things: 1) Try 4.16 SDK 2) Attach full error stack from error log view.
Created attachment 283294 [details] Stack trace for NPE when disabling null analysis
Added the full stack trace. The problem still occurs on 4.15 SDK. I'm currently in the process of trying 4.16.
Upgrading to 4.16RC2 seems to have helped but not entirely eliminated the problem. It is now only triggering unnecessary full rebuilds occasionally rather than every time.
Sorry, should have mentioned the NPE still occurs.
(In reply to Matthew Daggitt from comment #5) > Sorry, should have mentioned the NPE still occurs. Please attach the stack trace. Ideally you could also try to isolate the smallest possible source that reproduces the problem.
Created attachment 283368 [details] Stack trace for NPE when disabling null analysis in 4.16
I've added the stack trace for 4.16. Apologies, I'm having difficulty isolating it. Once I start removing projects and source files it appears to become non-deterministic. Sometimes I remove one of our projects and it disappears, but then when I revert the state and remove the project again it still persists. One thing that might be a little unusual about our setup is that we have 3 projects X, Y, Z (where X is on the build path of Y and Y is on the build path of Z) in which X and Z do not use null annotations but Y does. Unsure if that's relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
