tesla / m2eclipse-ajdt Goto Github PK

Would be great to have some use doc. to read whar shall work and what not.
We don't get any cross references showed for a current project ascpect file we have open in eclipse editor and which is weaved on a dependeny defined in projetcs pom file.

We use latest eclipse indigo, latest ajdt, latest m2e, external maven 3.03 installation.
It only works if we have all projects come together via maven modules, but not when weaving current projetcs aspect on installed depedency or current projects java code get weaved on by an installed depedency aspect artifact.

ITs hard to say how and weh this stuff should works, because there is no howto or user guide documenting how this shall work.

Because the src/main/aspect directory is not declared in the test pom.

I have reported this issue on stackoverflow and in the aspectj mailing lists.

Basically, when I put aspects in my test source folder (src/test/java) Eclipse (with the m2e compiler) will weave the aspect into classes from the main source folder (src/main/java). See https://github.com/benze/aspectj-maven-plugin-defect-example.

The goal is to have an aspect from my src/test/java path woven into my classes from src/main/java but output only in my target/test-classes. The reasoning behind this is that the aspect is only used for junit testing and not for normal code compilation/use.

When I build from the command line, everything works properly. The "compile" goal compiles & weaves all my src/main/java files to the target/classes output directory and the "test-compile" compiles & weaves all my src/test/java files into target/test-classes.

However, when I build from within Eclipse, my Aspects in src/test/java are woven into classes in target/classes as well (see target/classes/com/test/ServiceImpl.class. With the decompiler, I can see the MangleAspect has been woven in. Additionally, only the files from src/test/java are output into target/test-classes while the pom instructs ajc to do otherwise (weave all class files from target/classes into target/test-classes).

I noticed, however, if I disable the m2e connector and just use lifecycle mapping within my pom directly that instructs the aspectj plugin to execute on compile/test-compile goals, my output seems to be as I would expect. Can this be an m2e connector issue? I'm not entirely clear on how this connector works, or how it is injected into the m2e maven compile process.