Bug 81617 - Adding aspectj nature to a project with generic classes pre'vents java files to be compiled
Summary: Adding aspectj nature to a project with generic classes pre'vents java files ...
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 1.2.0 M2   Edit
Hardware: PC Windows XP
: P5 major (vote)
Target Milestone: 2.0.1   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-19 14:30 EST by Christophe Avare CLA
Modified: 2009-09-24 18:25 EDT (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 Christophe Avare CLA 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 CLA 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 CLA 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 CLA 2009-09-24 18:25:25 EDT 
Old bug.  Likely fixed for a while.