Hi Andy,
Thanks for the reply. Are you saying that there is no way in Eclipse to differentiate which are test classes and which are source classes?
I'm actually seeing a behaviour that I find troubling.
If I compile my code from the command line, I get a [Xlint:adviceDidNotMatch] when ajc runs my test-classes. Consequently, my aspect is never woven into my class. But when I compile from within Eclipse, the aspect is woven in.
I suspect that it has something to do with the classpath that maven is presenting to ajc; indeed when I enable debug information, I see that the /src/main/java classes are not on the path to ajc as they are during the regular compilation, and only the src/test/java classes are present.
I don't know if this is a limitation of the ajc compiler, or if there is a way to tell it to additionally (re)compile / weave classes into the output folder only if they are affected. I see the '-inpath' argument to ajc, but will dump everything in the inpath to the output directory, or only the changed classes? Is there a way to tell it only to put the classes into the output directory if they are changed/modified?
Thanks,
Eric