Bug 256400 - An internal error occurred during: "Delete and update AspectJ markers for CoreSource".
Summary: An internal error occurred during: "Delete and update AspectJ markers for Cor...
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: IDE (show other bugs)
Version: 1.6.1   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 1.6.3   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-25 04:51 EST by Piers CLA
Modified: 2008-11-27 12:59 EST (History)
2 users (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 Piers CLA 2008-11-25 04:51:17 EST 
this occured during a clean and build of the project i'm working on. The following was inthe details.

An internal error occurred during: "Delete and update AspectJ markers for CoreSource".
java.lang.NullPointerException
Comment 1 Piers CLA 2008-11-25 04:55:22 EST 
I did another clean and build (without changing anything) and no more errors were encountered.
Comment 2 Andrew Eisenberg CLA 2008-11-25 11:09:29 EST 
Do you have a stack trace or anything?
Comment 3 Piers CLA 2008-11-25 12:15:47 EST 
(In reply to comment #2)
> Do you have a stack trace or anything?
> 

Only what was in the details of the error dialog as stated above.

"An internal error occurred during: "Delete and update AspectJ markers for
CoreSource".
java.lang.NullPointerException"
Comment 4 Andrew Eisenberg CLA 2008-11-25 19:06:48 EST 
This is actually an AspectJ problem.  The problem lies here:

JDTLikeHandleProvider.java : line 163

the line is:
if (sig1 == null && ipeSig == null || sig1.equals(ipeSig)) {

but this can throw a null pointer exception.

should be this instead:
if ((sig1 == null && ipeSig == null) || (sig1 != null && sig1.equals(ipeSig))) {


MOving this over to AspectJ.
Comment 5 Andrew Eisenberg CLA 2008-11-25 19:08:08 EST 
Bumping priority becuase this is an easy fix that whose consequences are large.
Comment 6 Andrew Clement CLA 2008-11-27 12:59:26 EST 
would have liked a testcase, but I've committed the change anyway.