Community
Participate
Working Groups
Can't compile AspectJ project if compiler compliance level is set to 6.0 There are such errors "parameterized types are only available if source level is 5.0" "for each statements are only available if source level is 5.0" and so on Version: 1.5.0.200609110659 AspectJ version: 1.5.3.200608290814
*** Bug 157667 has been marked as a duplicate of this bug. ***
I do wonder if this should be high priority bug, since JDK 6 is already out. We are planning to upgrade to JDK 6 but we are kind of stopped because of this issue.
*** Bug 172272 has been marked as a duplicate of this bug. ***
*** Bug 173968 has been marked as a duplicate of this bug. ***
I have reported this bug FIVE months ago, but nothing was done to solve it. Does anyone read this mail? We have to use java 6 due to fine fonts on LCD monitors, since our customer don't saticfied with font quality under java 5. We use AOP heavily in our project, so we can't release it until this bug is fixed. Is there any hope that it will be fixed in near future or should we throw away all the AOP stuff from our project while not too late?! Sorry for such a post, but we are in troubles for that reason. Sincerely yours, Vladimir Borkovkin
Yes, we see all comments attached to all bugzilla entries - I am sorry we haven't done more to keep you informed. This is not a bug, AspectJ is a Java5 based compiler, not a Java6 based compiler - this is an enhancement request for moving up to a java6 compiler base (ie. the Eclipse 3.2 compiler), that is a non-trivial piece of work that has so far not been a top priority compared to bugs we have in the Java5 support. For your particular case, do you utilise the alternative font system by calling new APIs that only exist in the Java6 runtime? If so can you simply change your project to use the 1.6 runtime library rather than the 1.5 library? (and keep it as a 1.5 project??)
Hello, We also have to use java 6 due to scripting enhancements and we have got the same problems when compiling. I think that this feature is very important since JDK 6 has been out for several months. In your last message (in february 2007), you were talking about a point that "has so far not been a top priority". Can you give some more precision about the fixing date? We use AspectJ for all our JUnit tests (with virtual mocking) and it would be dramatic for us to wait for months. Sincerely yours, Emile Vauge (In reply to comment #6) > Yes, we see all comments attached to all bugzilla entries - I am sorry we > haven't done more to keep you informed. This is not a bug, AspectJ is a Java5 > based compiler, not a Java6 based compiler - this is an enhancement request for > moving up to a java6 compiler base (ie. the Eclipse 3.2 compiler), that is a > non-trivial piece of work that has so far not been a top priority compared to > bugs we have in the Java5 support. > > For your particular case, do you utilise the alternative font system by calling > new APIs that only exist in the Java6 runtime? If so can you simply change > your project to use the 1.6 runtime library rather than the 1.5 library? (and > keep it as a 1.5 project??) >
Another 4 months passed by since the last comment on this entry. I was trying to locate a road map for the AspectJ development did not succeed. What are the current plans to move towards Java 6? Is there a road map for AspectJ available that someone could point me to?
there will be an announcement very soon about the roadmap for AspectJ - probably within the next couple of weeks. I'll try and remember to put a pointer to it in this bug when its available.
finally on the radar!
Glad to see this moving forwards, and I can understand how things have been prioritised. I am deploying to Java6, and not finding any problems with having my compiler levels at Java5. More importantly, I'd suggest that the team be prepared for Java7, as there will be notable new language features to support. The lack of Java7 support when it comes will mean that it will hold me back from the Java7 features I'll be eager to use. Keep smilin' folks!
This is fixed in the latest AJDT 1.5.2 dev builds for Eclipse 3.3 - available from the dev download site and update site: http://www.eclipse.org/ajdt/downloads/ http://download.eclipse.org/tools/ajdt/33/dev/update This includes AspectJ1.6.0m1
Seems to work for me - thank you!
