You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (Jira)" <ji...@apache.org> on 2021/09/07 18:46:00 UTC
[jira] [Commented] (MCOMPILER-407) Feature request: In debug mode,
print full output of javac (including stdout)
[ https://issues.apache.org/jira/browse/MCOMPILER-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411421#comment-17411421 ]
Robert Scholte commented on MCOMPILER-407:
------------------------------------------
That's handled per compiler in https://github.com/codehaus-plexus/plexus-compiler
> Feature request: In debug mode, print full output of javac (including stdout)
> -----------------------------------------------------------------------------
>
> Key: MCOMPILER-407
> URL: https://issues.apache.org/jira/browse/MCOMPILER-407
> Project: Maven Compiler Plugin
> Issue Type: New Feature
> Affects Versions: 3.8.1
> Reporter: Manu Sridharan
> Priority: Major
>
> Certain javac annotation processors and plugins like [The Checker Framework|https://checkerframework.org/] sometimes print useful diagnostics on stdout. Currently, there is no way to see this output using the Maven Compiler Plugin, even when Maven is run with the -X option. I suggest that when Maven is in debug mode, the plugin should show as a debug message the full stdout of javac. This should also work if javac is forked.
> If someone points me at the relevant code, I am happy to try to submit a pull request for this change.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)