You have two options with AspectJ if you want to avoid it compiling from source:
1) Use LTW with the weaving agent. 2) Move your aspects into a separate Maven module. Compile your Java modules with the normal Maven Compiler Plugin and the aspect module with AspectJ Maven. Then create another module which just uses AspectJ Maven in order to do binary weaving on a Java module, using both previously created artifacts as dependencies. In this scenario you need to make sure that JaCoCo offline instrumentation is bound to a phase before binary weaving is done. The easiest way out, though, would be to test your aspects in isolation and also the Java code without aspects and measure coverage there without any issues. -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/d696cd6e-7118-4893-8698-39774996e51c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
