If the app contains an aop.xml and aspectjweaver.jar it seems reasonable to expect that the user wants to attach the weaver as an agent. The only tricky question to settle is where to look for aop.xml, taking into account that jar files can also bring their own. Maybe we should ignore the jar files and assume that the user will place her own aop.xml in an "obvious" place (in META-INF or org/aspectj or the corresponding locations inside BOOT-INF/classes).
We'd need an escape hatch to back out (e.g. if the user actually already wove the classes and the weaver is accidentally present, or just to test the difference between AspectJ and Spring AOP).
If the app contains an
aop.xmlandaspectjweaver.jarit seems reasonable to expect that the user wants to attach the weaver as an agent. The only tricky question to settle is where to look foraop.xml, taking into account that jar files can also bring their own. Maybe we should ignore the jar files and assume that the user will place her ownaop.xmlin an "obvious" place (inMETA-INFororg/aspectjor the corresponding locations insideBOOT-INF/classes).We'd need an escape hatch to back out (e.g. if the user actually already wove the classes and the weaver is accidentally present, or just to test the difference between AspectJ and Spring AOP).