I have a project which uses (successfully) the AspectJ maven plugin during
compilation.
We also use the maven eclipse plugin to generate eclipse projects files. With
appropriate nature and build command setups everything usually works fine.
Except when the source has compile errors!
I use folowing AspectJ plugin configuration:
<plugin>
<!-- aspectJ configuration -->
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>compile</goal>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
<configuration>
<source>1.5</source>
<target>1.5</target>
<argumentFileName>${artifactId}-aj.args</argumentFileName>
</configuration>
</plugin>
When I run the command line mvn eclipse:eclipse
The AspectJ compile phase kicks in first and if there are source code problems,
fails the build on the compilation fault before the eclipse project files can
be generated.
In a standard maven Java project (Without the AspectJ plugin), the java
compiler is NOT invoked when I use the eclipse:eclipse target, and so the
project files are generated correctly even if there are compile faults in the
code.
Is there someway to disable the AspectJ compile with a command line switch or
is there something else I need to do to ensure that the AspectJ compile is not
triggered except when a compile is actually required?
Any help would be gratefully received!
Ian
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
