Bug 171667 - When ordering a Clean with Build Automatico I receive the error below.
Summary: When ordering a Clean with Build Automatico I receive the error below.
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.5.3   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: 1.5.4   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-25 09:24 EST by George Queiroz CLA
Modified: 2007-10-10 10:21 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 George Queiroz CLA 2007-01-25 09:24:17 EST 
When executing an Clean Project in Eclipse with Automatic Building I receive the error below.

line from the top stack, e.g. "SomeFile.jara:243"

java.lang.NullPointerException
at org.aspectj.ajdt.internal.compiler.problem.AjProblemReporter.methodMustOverride(AjProblemReporter.java:380)
at org.aspectj.org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.resolveStatements(MethodDeclaration.java:153)
at org.aspectj.org.eclipse.jdt.internal.compiler.ast.AbstractMethodDeclaration.resolve(AbstractMethodDeclaration.java:400)
at org.aspectj.org.eclipse.jdt.internal.compiler.ast.TypeDe ... pter.java:107)
at org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191)

NullPointerException thrown: null
Comment 1 Andrew Clement CLA 2007-01-29 11:02:49 EST 
Ideally I need a small example program that demonstrates the failure so i can fix it.  You seem to have ITDs that are being used to ensure a method is being overridden and that's what is causing the failure - if that helps you narrow it down to a test program?

Or, you can try deactivating pipeline compilation to see if that makes a difference, by setting "-Xset:pipelineCompilation=false" in the advanced compiler options in AJDT (in the pure text field) - but if that works it is only a workaround, switching off pipelining will greatly increase memory consumption.
Comment 2 Andrew Clement CLA 2007-02-16 05:04:33 EST 
I've put in guards that should stop this happening - i suspect it is us looking at a type munger to see if it provides a method in the supertype when it is not an ITD method munger and so should be ignored.
Comment 3 Andrew Clement CLA 2007-02-21 03:41:25 EST 
guards are in latest AJ dev build.