Bug 200652 - java.lang.NullPointerException at org.aspectj.weaver.bcel.BcelWeaver.raiseUnboundFormalError(BcelWeaver.java:833)
Summary: java.lang.NullPointerException at org.aspectj.weaver.bcel.BcelWeaver.raiseUnb...
Status: RESOLVED DUPLICATE of bug 203408
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: 2007-08-21 05:38 EDT by Thorsten Hilker CLA
Modified: 2007-09-19 04:29 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 Thorsten Hilker CLA 2007-08-21 05:38:35 EDT
Hi!

I'm using Eclipse 3.2 and 3.3 here.
If I do a "Build-Project" on an AspectJ-Project I get the following exception:

java.lang.NullPointerException
at org.aspectj.weaver.bcel.BcelWeaver.raiseUnboundFormalError(BcelWeaver.java:833)
at org.aspectj.weaver.bcel.BcelWeaver.validateSingleBranch(BcelWeaver.java:688)
at org.aspectj.weaver.bcel.BcelWeaver.validateBindings(BcelWeaver.java:627)
at org.aspectj.weaver.bcel.BcelWeaver.rewritePointcuts(BcelWeaver.java:556)
at org.aspectj.weaver.bcel.BcelWeaver.prepareForWeave(BcelWeaver.java:484)
at org.aspectj.ajd ... ob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Compile error: NullPointerException thrown: null

If I do a "Build-Clean" the exception does not appear and
the project compiles correctly.

Regards!

Thorsten
Comment 1 Andrew Clement CLA 2007-09-18 05:33:27 EDT
Are you using annotation style aspects and thisJoinPoint - you may be interested in bug 203408.
Comment 2 Thorsten Hilker CLA 2007-09-19 04:25:50 EDT

*** This bug has been marked as a duplicate of bug 203408 ***
Comment 3 Thorsten Hilker CLA 2007-09-19 04:27:23 EDT
Hi!

The Solution for Bug# 200652 worked for me.

Regards

Thorsten
Comment 4 Thorsten Hilker CLA 2007-09-19 04:29:47 EDT
(In reply to comment #3)
> Hi!
> 
> The Solution for Bug# 200652 worked for me.
> 
> Regards
> 
> Thorsten
> 

I mean Bug# 203408 of course.