[MCOMPILER-460] Compiler doesn't show detailed information with the Maven Toolchains

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.8.1
• Fix Version/s: 3.10.0
• Environment: Windows Java 16
• Assignee: Maarten Mulders
• Reporter: Johan Janssen
• Created: 10/Apr/21 19:47
• Updated: 09/Feb/22 12:24
• Resolved: 09/Feb/22 06:39

Description

I've created an example to showcase the issue: https://github.com/johanjanssen/mavenexample

When running without the Toolchains on Java 16

mvn compile or docker build -t mavenexample -f DockerfileJava16 .  

Gives 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project broken: Fatal error compiling: java.lang.IllegalAccessError: class lombok.javac.apt.LombokProcessor (in unnamed module @0x21bd20ee) cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @0x21bd20ee -> [Help 1]

When running with the Toolchains on Java 16

mvn compile -Ptoolchain or docker build -t mavenexample -f DockerfileJava16Toolchain . 

Gives 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project broken: Compilation failure -> [Help 1]

So the Toolchain setup lacks quite some information about the compilation failure.

Is it possible to get the same error information when using the toolchain?

My usecase is having a quick way to build the same code with 2 different versions of Java. To show one version works and the other fails. It's also possible with Docker or setting the JAVA_HOME variable. But I was curious to see if it would work with toolchains as well.