This is triggered by the Stack Overflow question No verbose output when fork option is used for maven-compiler-plugin.
The JavacCompiler is ignoring the standard output of the javac executable (thus ignoring the verbose configuration) when used in forked mode.
This is because in the method compileOutOfProcess, the CommandLineUtils.StringStreamConsumer out variable populated with the standard output is ignored when populating the resulting messages:
returnCode = CommandLineUtils.executeCommandLine( cli, out, err );
messages = parseModernStream( returnCode, new BufferedReader( new StringReader( err.getOutput() ) ) );
As suggested fix, the parseModernStream method should take both the result of the error output and standard output.
This is triggered by the Stack Overflow question No verbose output when fork option is used for maven-compiler-plugin.
The
JavacCompileris ignoring the standard output of the javac executable (thus ignoring the verbose configuration) when used in forked mode.This is because in the method
compileOutOfProcess, theCommandLineUtils.StringStreamConsumer outvariable populated with the standard output is ignored when populating the resulting messages:As suggested fix, the
parseModernStreammethod should take both the result of the error output and standard output.