Bug 162601 - NPE at AjProblemReporter.java:231
Summary: NPE at AjProblemReporter.java:231
Status: RESOLVED DUPLICATE of bug 166514
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-27 13:46 EDT by Felix Mayer CLA
Modified: 2006-12-07 10:19 EST (History)
1 user (show)

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 Felix Mayer CLA 2006-10-27 13:46:55 EDT 
What else can I say? This happends when my projects are rebuilt.

java.lang.NullPointerException
at org.aspectj.ajdt.internal.compiler.problem.AjProblemReporter.abstractMethodMustBeImplemented(AjProblemReporter.java:231)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.checkAbstractMethod(MethodVerifier.java:96)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.checkMethods(MethodVerifier.java:318)
at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.Method ... pter.java:107)
at org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191)

NullPointerException thrown: null
Comment 1 Matt Chapman CLA 2006-10-27 14:06:09 EDT 
Can you provide a testcase?
Passing over to compiler.
Comment 2 Felix Mayer CLA 2006-10-27 14:29:38 EDT 
Sorry, the problem happens randomly when my interdependent projects are recompiled. I just did a clean rebuild of the dependency chain, and the issue went away. Here is the entry from .log:

java.lang.NullPointerException
	at org.aspectj.ajdt.internal.compiler.problem.AjProblemReporter.abstractMethodMustBeImplemented(AjProblemReporter.java:231)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.checkAbstractMethod(MethodVerifier.java:96)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.checkMethods(MethodVerifier.java:318)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.verify(MethodVerifier.java:594)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.MethodVerifier15.verify(MethodVerifier15.java:397)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.verifyMethods(SourceTypeBinding.java:1565)
	at org.aspectj.org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.verifyMethods(CompilationUnitScope.java:728)
	at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:516)
	at org.aspectj.org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:329)
	at org.aspectj.ajdt.internal.core.builder.AjBuildManager.performCompilation(AjBuildManager.java:906)
	at org.aspectj.ajdt.internal.core.builder.AjBuildManager.doBuild(AjBuildManager.java:260)
	at org.aspectj.ajdt.internal.core.builder.AjBuildManager.batchBuild(AjBuildManager.java:176)
	at org.aspectj.ajde.internal.CompilerAdapter.compile(CompilerAdapter.java:107)
	at org.aspectj.ajde.internal.AspectJBuildManager$CompilerThread.run(AspectJBuildManager.java:191)
Comment 3 Helen Beeken CLA 2006-12-07 10:19:47 EST 
marking as duplicate of bug 166514 as they display the same stacktrace.

*** This bug has been marked as a duplicate of bug 166514 ***