The pom I was adding the definitions was an aggregation one and not a java one. This was the reason that the aspectj plugin reported that error. I added the definition in the children poms that interested me and it worked (after a while :-) ).
Best regards, Aggelos On Thu, Jul 26, 2012 at 3:37 PM, Aggelos Biboudis <bibou...@gmail.com>wrote: > Hello, > > I try to build an open source project (and while not important, the > project is an SOS service from http://52north.org/), with the AspectJ > maven plugin, in order to weave some aspects of mine. I am getting the "*Not > executing aspectJ compiler as the project is not a Java classpath-capable > package*" warning. My attempts to find adequate information around the > web, resulted in solutions around the version number of source/target. > While looking in mailing lists, every reference of this error, is > accompanied also with the "*bad version number found in ...*" warning. > Unfortunately I get only the "Not executing aspectJ compiler.." warning. > > My case is to build a war for tomcat deployment while using aspects on > certain operations. I have written an aspect, I placed it in a directory > named aspects/ and I have included the following dependency. > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>aspectj-maven-plugin</artifactId> > <version>1.4</version> > <dependencies> > <dependency> > <groupId>org.aspectj</groupId> > <artifactId>aspectjrt</artifactId> > <version>1.7.0</version> > </dependency> > <dependency> > <groupId>org.aspectj</groupId> > <artifactId>aspectjtools</artifactId> > <version>1.7.0</version> > </dependency> > </dependencies> > <configuration> > <verbose>true</verbose> > <showWeaveInfo>true</showWeaveInfo> > <includes> > <include>**/aspects/InterceptInsertCalls.aj</include> > </includes> > </configuration> > <executions> > <execution> > <phase>process-sources</phase> > <goals> > <goal>test-compile</goal> > <goal>compile</goal> > </goals> > <configuration> > <source>1.6</source> > <target>1.6</target> > </configuration> > </execution> > </executions> > </plugin> > > The output is the following: > > [INFO] --- aspectj-maven-plugin:1.4:compile (default) @ 52n-sos --- > [WARNING] Not executing aspectJ compiler as the project is not a Java > classpath-capable package > [INFO] > [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 52n-sos > --- > [INFO] Installing C:\development\Workspace\52n-sos\pom.xml to > C:\Users\biboudis\.m2\repository\org\n52\sensorweb\sos\52n-sos\3.5.0-M1\52n-sos-3.5.0-M1.pom > > How can my maven process be aware of the classpath environment, in order > the aspectj compiler to be invokedn seamlessly? As far as I have seen in > this<http://grepcode.com/file/repo1.maven.org/maven2/org.codehaus.mojo/aspectj-maven-plugin/1.4/org/codehaus/mojo/aspectj/AbstractAjcCompiler.java?av=f#357> > if-condition, > from the plugin's internals, should I define a custom component like this? > > <component> > <role>org.apache.maven.artifact.handler.ArtifactHandler</role> > <role-hint>war</role-hint> > <implementation>org.apache.maven.artifact.handler.DefaultArtifactHandler > </implementation> > <configuration> > <type>war</type> > <includesDependencies>true</includesDependencies> > *<language>java</language>* > <addedToClasspath>false</addedToClasspath> > </configuration> > </component> > > I am no expert of Maven (actually this is my first time ever through this > building tool), so this is the deepest path I could dive to. I would > be grateful, if someone could guide me through the correct direction. > > Thank you in advance, > Aggelos Biboudis > -- Doctoral Researcher, University of Athens http://www.di.uoa.gr/~biboudis/ <http://www.di.uoa.gr/%7Ebiboudis/>
