Community
Participate
Working Groups
Compiler should produce an error when it encounters a concrete @AspectJ aspect that is also parameterized. This way @AspectJ aspects will have the same behavior as their code-style counterpart (which correctly do produce an error). Currently, generic concrete aspects such as the following are silently ignored (i.e. advice in them don't apply). package tracing; import org.aspectj.lang.JoinPoint; import org.aspectj.lang.annotation.Aspect; import org.aspectj.lang.annotation.Before; import org.aspectj.lang.annotation.Pointcut; @Aspect public class TracingAspect2<T> { @Pointcut("execution(* *(..))") public void traced() {} @Before("traced()") public void log(JoinPoint thisJoinPoint) { System.out.println("Entering "); } }
Do this if it doesn't cost too much to calculate
fixed - message comes out 'late' (as in during weaving rather than compiling) so we can catch those using javac and trying to sneak it in that way ;) This is the 35th bug I've addressed in two days, 1.6.1 is looking great.