Community
Participate
Working Groups
The current AspectJ 5 LTW specification allows simple concrete aspects to be defined in aop.xml. They may extend an abstract aspect and define a single "scoping" pointcut. I think it would be very useful to be able to declare aspect precedence in a similar way allowing aspects to be deployed without any specific precedence leaving any decision to a systems administrator. The syntax might look like this: <aspectj> <aspects> <concrete-aspect name="com.xyz.MyPrecedence" precedence="*..*Security*, Logging+, *" /> </aspects> </aspectj> Any potential conflicts are already handled by the compiler.
so in that case we just need to spot: - a <concrete-aspect without extends attribute, and with NO nested pointcut, but with a precedence clause (else it would be a NOOP aspect) then we just do a codegen for @DeclarePrecedence(your precedence) @Aspect public class ...theName... /*no extends*/ { //nothing } planning for RC1, as precedence attribute is already impl. for regular concrete-aspect.
impl
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.
