Community
Participate
Working Groups
I get this error on every file save: java.lang.NullPointerException at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ImplicitNullAnnotationVerifier.checkImplicitNullAnnotations(ImplicitNullAnnotationVerifier.java:98) at org.aspectj.org.eclipse.jdt.internal.compiler.ast.MessageSend.resolveType(MessageSend.java:807) at org.aspectj.org.eclipse.jdt.internal.compiler.ast.Expression.resolve(Expression.java:1020) at org.aspectj.org.eclipse.jdt.internal.compiler.ast.AbstractMeth ... AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Compile error: NullPointerException thrown: null This is my installation version: AspectJ Compiler Source Code 1.8.5.20150128171000 org.aspectj.source.feature.group Eclipse AspectJ Development Tools AspectJ Development Tools (AJDT) Source Code 2.2.4.e44x-20150202-1700 org.eclipse.ajdt.source.feature.group Eclipse AspectJ Development Tools
Any chance you can share a small project with me that exhibits this behavior? It is something to do with the characteristics of your project will be hard to pin down without recreating. Possibly it is something already fixed in JDT and we haven't picked up the fix yet. Are you using the null analysis jdt feature?
Yes, I just figured this out today. I went to Preferences > Java > Compiler > Errors/Warnings > Null Analysis and unchecked "Enable annotation-based null analysis" that got rid of the problem. But, it's a shame because I really like the annotation based null analysis. I don't know what could be causing the issue in my project, but probably that feature is definitely part of it.
(In reply to Andrew Clement from comment #1) > Any chance you can share a small project with me that exhibits this > behavior? It is something to do with the characteristics of your project > will be hard to pin down without recreating. Possibly it is something > already fixed in JDT and we haven't picked up the fix yet. Are you using the > null analysis jdt feature? Yes, I just figured this out today. I went to Preferences > Java > Compiler > Errors/Warnings > Null Analysis and unchecked "Enable annotation-based null analysis" that got rid of the problem. But, it's a shame because I really like the annotation based null analysis. I don't know what could be causing the issue in my project, but probably that feature is definitely part of it.