Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317633 - NPE during incremental compilation
Summary: NPE during incremental compilation
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.9   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 1.6.9RC1   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 15:21 EDT by Andrew Clement CLA
Modified: 2010-06-23 13:18 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Clement CLA 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 CLA 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.