Community
Participate
Working Groups
This is really a re-hash of bug 67051. In fact, this is not a jdk 1.5 bug but a 1.5 change. It has to do with the fact that co-variant return types result in more generated methods in the class file. In the case of StringBuffer.toString() the old behavior is the wrong behavior. We dealt with this exact issue at our company. The solution is, apparently, to ignore bridge methods from the class, which are now flagged as such. Without this fix, much 1.5 code will not compile.
AspectJ 1.2 is a Java 1.4 compiler right now (with an option to behave as a 1.3 compiler). At its core we are based on a particular level of the Eclipse Compiler. When Eclipse moves to full 1.5 support we will in turn move to supporting 1.5. I believe the 1.5 compiler compiles its 'new features' into bytecode that is backwards compatible, so AspectJ should work in binary weaving mode when applying aspects to code compiled with a 1.5 compiler. So, I guess I'm saying that supporting java source code that uses 1.5 language features is an enhancement request that we will get to shortly.
I have raised an enhancement request (bug 71548) for AspectJ to handle Java 1.5 source code. *** This bug has been marked as a duplicate of 71548 ***
Fix released as part of AspectJ 1.2.1
