Closed jmirc closed 8 years ago
snicoll
commented
8 years ago Does it matter if it's a multi-modules project (since you mentioned it explicitly). It would help if you could share a sample or at least your maven-compiler-plugin configuration (I can see you're using APT and I'd like to know if you get the same error with the standard compiler).
jmirc
commented
8 years ago I will try to share a sample soon.
Here are our maven configuration.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>${java.version}</source>
<target>${java.version}</target>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>1.8</version>
<configuration>
<Xlint>ignore</Xlint>
<complianceLevel>1.8</complianceLevel>
<aspectLibraries>
<aspectLibrary>
<groupId>expedia.content.solutions.metrics</groupId>
<artifactId>aspectj-support</artifactId>
</aspectLibrary>
</aspectLibraries>
<includes>
<include>**/*.java</include>
</includes>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
</plugin>that does not help much I am afraid, there is nothing that indicates where JDT comes from. Or do you get that issue when you compile in Eclipse or something?
Actually scratch that, the aspectJ compiler is running the annotation processor and it runs again with the regular compiler I guess.
jmirc
commented
8 years ago It was an issue in our pom.xml. Sorry for the spam.
snicoll
commented
8 years ago can you share what the issue was please?
jmirc
commented
8 years ago I just updated the aspectJ plugin
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>aspectj-maven-plugin</artifactId>
<version>1.8</version>
<configuration>
<showWeaveInfo/>
<forceAjcCompile>true</forceAjcCompile>
<Xlint>ignore</Xlint>
<complianceLevel>1.8</complianceLevel>
<sources/>
<weaveDirectories>
<weaveDirectory>${project.build.directory}/classes</weaveDirectory>
</weaveDirectories>
</configuration>
<executions>
<execution>
<goals>
<goal>compile</goal>
<goal>test-compile</goal>
</goals>
</execution>
</executions>
</plugin>
hanusto
commented
8 years ago For me
snicoll
commented
8 years ago @hanusto this issue is closed. This is a build setup issue and not related to Spring Boot. I am happy to improve the doc to help users setup stuff. I had a look to your project and I am confused as what the problem is. The meta-data is generated and the build works for me. If you're still having a question, please ask on stackoverflow.
markdathorne
commented
6 years ago Thank you, jmirc. I lost more than a couple of days over this and your params got my build working in Tomcat again! Muchas gracias, buddy.
t-beckmann
commented
6 years ago The root cause is an Eclipse Java Compiler (EJC) incompatibility, the AspectJ Compiler (AJC) is based in it. I files a bug report and suggested an easy fix at https://bugs.eclipse.org/bugs/show_bug.cgi?id=530665.
I have a project using AspectJ and enabled the spring-boot-configuration-processor plugin.
SpringBoot: 1.3 AspectJ: 1.8.6 Maven: Multiple modules
When I compile my project using maven, I got the following exception