AspectJ & Maven warning: "Advice defined in ... has not been applied?"

Question

I'm trying to weave some aspects at compile time into a project that becomes a WAR. The aspects advise classes that are within the same project (though in different packages). I get the warning: ``` Advice not applied ``` My aspect is not being executed. Here's my setup: annotation FooAnnotation.java: ``` package a; @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.METHOD) public @interface FooAnnotation {} ``` aspect FooAdvice.aj: ``` package a; public aspect FooAdvice { private static final Log log = LogFactory.getLog(FooAdvice.class); Object around() : call( @FooAnnotation * *(..)) { log.info(String.format("Testing around")); return proceed(); } } ``` I also tried the annotation: ``` @Around("call( @FooAnnotation * *(..))") public Object checkFoo( ProceedingJoinPoint joinPoint) throws Throwable { ``` As far as I can tell, my pointcut specification is correct, but for some reason the ajc compiler isn't playing ball. Class FooClass.java: ``` package b; @ApplicationPath("/servic…

Accepted Answer

Aha! Found the answer here:

aspectj: why advice cannot be applied?

It has nothing to do with maven.

The reason is that in my example, the method is being called from within the jax-rs framework by indirect loading. The `call()` advice wants to weave the caller, but the ajc compiler can't know where the caller is. The fix is to change the advice to `execution()` thusly:

```
Object around() : execution(@FooAnnotation * *(..)) {...}
```

This differs because it weaves around the execution (which ajc can find), rather than the caller.

Done.

AspectJ & Maven warning: "Advice defined in ... has not been applied?"

Solution

Problem