[jira] [Commented] (MTOOLCHAINS-37) Toolchain plugin does not show compile errors in Windows 10

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MTOOLCHAINS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17822834#comment-17822834 ] 

Elliotte Rusty Harold commented on MTOOLCHAINS-37:
--------------------------------------------------

This is going to be hard to impossible to debug remotely. I really do doubt it has anything to do with the toolchains plugin. Just maybe it has something to do with the maven-compiler-plugin, but as you surmise this is mostly an idiosyncrasy in your local environment.

The question I will ask is what happens if you call the same javac directly rather than using Maven at all? Does the output show up then?

> Toolchain plugin does not show compile errors in Windows 10
> -----------------------------------------------------------
>
>                 Key: MTOOLCHAINS-37
>                 URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-37
>             Project: Maven Toolchains Plugin
>          Issue Type: Bug
>         Environment: Windows 10 (version 1909)
>            Reporter: Francois Loriot
>            Priority: Minor
>
> I have recently tried to build some java projects on Windows 10 using the toolchain plugin, but I see that when there are java compilation errors, the output of the build does not list the errors.  The same build with identical setup on Windows 7 correctly shows the errors.  I'm running Maven with Oracle JDK 1.8 (I have also tried Open JDK 1.8 and Oracle 9) and the toolchain for the compilation points to IBM SDK 1.6 (I have also tried SDK 1.6 and 1.8).
> I'm using the default/latest toolchain and compiler plugins.  
> I have also noticed that every time the compiler is being called during the build, it briefly pops up a command prompt window with some output.  I'm thinking the actual error description in case of java errors goes in these windows, instead of the build output.
> I can reproduce the same behavior running the maven goals from within JetBrains Intelli J.
> I have confirmed the same behavior with other developers in my company.
> Running with -X or -e did not help either.
> Here is an example:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.7.0:compile (default-compile) on project ebill-webcommon: Compilation failure ->  *===== MISSING THE ERRORS HERE =======* [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :ebill-webcommon
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)