Bug 252102 - [plan] Internal Compiler Error at EclipseSourceType.java:640
Summary: [plan] Internal Compiler Error at EclipseSourceType.java:640
Status: RESOLVED DUPLICATE of bug 238992
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.6.3   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-25 15:32 EDT by Yury Hushchyn CLA
Modified: 2008-11-28 19:52 EST (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 Yury Hushchyn CLA 2008-10-25 15:32:06 EDT
Project build fails with the following exception:

org.aspectj.ajdt.internal.compiler.lookup.EclipseSourceType$MissingImplementationException
at org.aspectj.ajdt.internal.compiler.lookup.EclipseSourceType.generateAnnotation(EclipseSourceType.java:640)
at org.aspectj.ajdt.internal.compiler.lookup.EclipseSourceType.convertEclipseAnnotation(EclipseSourceType.java:609)
at org.aspectj.ajdt.internal.compiler.lookup.EclipseSourceType.getAnnotations(EclipseSourceType.java:590)
at org.aspectj.wea ... ementationException thrown: Please raise an AspectJ bug.  AspectJ does not know how to convert this annotation [@org.aspectj.lang.annotation.Aspect()]

Code caused the problem:

import javax.swing.SwingUtilities;

public privileged aspect RunMethodOnEventThread
{
  pointcut eventThreadMethods() : execution(* *.*(..)) && @annotation(OnEventThread);

  void around() : eventThreadMethods()
  {
    SwingUtilities.invokeAndWait(new Runnable()
    {
      public void run()
      {
        proceed();
      }
    };
  }
}

Annotation used in the code above:

@Target(ElementType.METHOD) public @interface OnEventThread
{
}
Comment 1 Andrew Clement CLA 2008-11-28 19:52:08 EST
Based on the line numbers listed for the stack trace, I don't think this was created on AspectJ 1.6.2 final.  The line numbers match up for EclipseSourceType for version 1.66 of that file which was just a dev build of 1.6.2.  Since then the code has been changed and actually the line that throws the exception MissingImplementationException has since been deleted - so this can't happen any more with 1.6.2 final or later.

In fact I believe this is a dup of bug 238992 - see comment 11 in that bug which lists the same stack trace and text for the error.

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