Bug 81617

Summary:	Adding aspectj nature to a project with generic classes pre'vents java files to be compiled
Product:	[Tools] AJDT	Reporter:	Christophe Avare <christophe.avare>
Component:	Core	Assignee:	AJDT-inbox <AJDT-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P5	CC:	pombredanne
Version:	1.2.0 M2
Target Milestone:	2.0.1
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Christophe Avare

2004-12-19 14:30:01 EST

When the aspectj nature is added to a java / plugin project which contains
generic types, the compiler does not recognize the Java 5 constructs in the java
files even if the 1.5 weaving behavior is enabled.
Error messages like:

Syntax error on tokens, delete these tokens,
The interface XXX cannot define an initializer,
Syntax error on tokens, AspectHeaderName expected instead

are generated in the problem view.

Removing the aspectj nature get back to the normal situation.

Comment 1 Matt Chapman

2004-12-19 17:34:52 EST

Hi, I'm afraid that just is the current state of AspectJ 1.5.0 M1. From the
AspectJ 5 Readme:

  ...
  These are implemented as changes to the weaver, not the front-end compiler. The   
  1.5.0 M1 release cannot be used to compile code using Java 5 features, but can 
  be used to weave (inpath) Java classes created by a Java 5 compiler.

Comment 2 Eclipse Webmaster

2009-08-30 02:51:10 EDT

LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.

Comment 3 Andrew Eisenberg

2009-09-24 18:25:25 EDT

Old bug.  Likely fixed for a while.