Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317633

Summary:	NPE during incremental compilation
Product:	[Tools] AspectJ	Reporter:	Andrew Clement <aclement>
Component:	Compiler	Assignee:	aspectj inbox <aspectj-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.6.9
Target Milestone:	1.6.9RC1
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Andrew Clement

2010-06-22 15:21:20 EDT

java.lang.NullPointerException at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.initialize(ParameterizedTypeBinding.java:702)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.<init>(ParameterizedTypeBinding.java:43)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createParameterizedType(LookupEnvironment.java:769)
at org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.makeTypeBinding1(EclipseFactory.java:676)
at org.aspectj.ajdt.internal.compiler.lookup.EclipseFactory.makeTypeBinding(EclipseFactory.java:591)

this occurs on an incremental build when the project has other problems - namely there is a parameterized type and one of the type arguments is of a type that does not exist.

Comment 1 Andrew Clement

2010-06-23 13:18:28 EDT

Changed EclipseFactory to return a 'ProblemReferenceBinding' with reason NOTFOUND if a type lookup fails.  This avoids the NPE.