Bug 463231 - AspectJ Internal Compiler Error ImplicitNullAnnotationVerifier.java:98
Summary: AspectJ Internal Compiler Error ImplicitNullAnnotationVerifier.java:98
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.8.5   Edit
Hardware: PC Mac OS X
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-26 14:39 EDT by Adam Rich CLA
Modified: 2015-03-26 19:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Rich CLA 2015-03-26 14:39:08 EDT
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
Comment 1 Andrew Clement CLA 2015-03-26 18:50:44 EDT
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?
Comment 2 Adam Rich CLA 2015-03-26 19:07:53 EDT
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.
Comment 3 Adam Rich CLA 2015-03-26 19:08:15 EDT
(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.