Bug 353900 - Java7 @annotation pointcut expression not working
Summary: Java7 @annotation pointcut expression not working
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.6.11   Edit
Hardware: PC Windows XP
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-04 10:50 EDT by Missing name CLA
Modified: 2011-11-22 15:22 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2011-08-04 10:50:56 EDT
When using Java7 with 1.7 compliance setting, the eclipse aspectj compiler plugin and the ant iajc task throw the following error:

--------------------------
the @annotation pointcut expression is only supported at Java 5 compliance level or above
--------------------------

It seems aspectj does not know Java7 yet. :)
Comment 1 Andrew Clement CLA 2011-08-04 11:04:40 EDT
> It seems aspectj does not know Java7 yet. :)

No, it doesn't.  you have to wait until I port AspectJ to Eclipse 3.7.1 - and 3.7.1 isn't due out for a couple of months.
Comment 2 Jesse Englert CLA 2011-09-23 19:05:23 EDT
This issue is blocking our company from moving some projects to Java7. Since Eclipse 3.7.1 was released today is there an estimate on when AspectJ will be upgraded to work with it?
Comment 3 Andrew Clement CLA 2011-09-23 19:49:47 EDT
In recent dev builds I fixed the problem with not tolerating a 1.7 compliance level - so it will now no longer produce errors like the one shown here.  (try the latest dev build or AJDT dev build).

It isn't a 1.7 compiler though, so you can't use 1.7 syntax.   Do you need 1.7 syntax? or just to avoid errors like the one shown here?
Comment 4 Jesse Englert CLA 2011-09-27 13:31:07 EDT
We just need to avoid errors like this one. We're compiling our aspects separately with iajc and using load time weaving while compiling our java files with javac. In this scenario do you see any issues with our java files using 1.7 syntax while our aspects use 1.6 syntax?

I didn't realize the dev build solved this error; thanks for the update.
Comment 5 Andrew Clement CLA 2011-09-28 16:17:41 EDT
I think that way of working will be OK with recent dev builds.  Do let me know if you see an issue though.