You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexander Kriegisch (Jira)" <ji...@apache.org> on 2023/12/16 05:14:00 UTC

[jira] [Created] (MCOMPILER-566) Display forked compiler stacktrace on error

Alexander Kriegisch created MCOMPILER-566:
---------------------------------------------

             Summary: Display forked compiler stacktrace on error
                 Key: MCOMPILER-566
                 URL: https://issues.apache.org/jira/browse/MCOMPILER-566
             Project: Maven Compiler Plugin
          Issue Type: Improvement
    Affects Versions: 3.11.0
            Reporter: Alexander Kriegisch


When analysing MCOMPILER-424, at some point I wanted to know what happens if I set {{fork=true}} or {{forceJavacCompilerUse=true}}. The result was bad: No matter if I compile with {{mvn -e -X}} or {{verbose=true}}, I only see a {{CompilationFailureException: Compilation failure}}. There seems to be no way to actually see the underlying root cause. I have to compile in process via Plexus {{JavaxToolsCompiler}} to see the {{AnnotationTypeMismatchException}} from [this comment|https://issues.apache.org/jira/browse/MCOMPILER-424?focusedCommentId=17797351&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17797351].



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