Open ArloL opened 9 years ago
The Maven Toolchains Plugin allows to e.g. define a different JDK for the compilation than the one being used to run maven.
While testing I noticed that the apt-maven-plugin does not support it. The build was running with JDK 1.7 and the toolchains-plugin required JDK 1.8.
<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-toolchains-plugin</artifactId> <executions> <execution> <goals> <goal>toolchain</goal> </goals> </execution> </executions> <configuration> <toolchains> <jdk> <version>1.8</version> </jdk> </toolchains> </configuration> </plugin>
The output:
[INFO] --- apt-maven-plugin:1.1.3:process (default) @ evocom-webapp --- D:\Daten\okeeffe\MyProjects\evocom-develop\workspace\evocom\evocom-webapp\src\main\java\de\evosec\ev ocom\server\configurations\ProfileConfiguration.java:22: error: illegal start of expression securityExecutor.execute(() -> dataInitializer.intializeData()); ^ ... 43 errors
The build is successful when executed with JDK 1.8.
It would be great if the apt-maven-plugin supported the maven-toolchains-plugin.
The Maven Toolchains Plugin allows to e.g. define a different JDK for the compilation than the one being used to run maven.
While testing I noticed that the apt-maven-plugin does not support it. The build was running with JDK 1.7 and the toolchains-plugin required JDK 1.8.
The output:
The build is successful when executed with JDK 1.8.
It would be great if the apt-maven-plugin supported the maven-toolchains-plugin.