[
https://issues.apache.org/jira/browse/MCOMPILER-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte moved MTOOLCHAINS-30 to MCOMPILER-388:
-----------------------------------------------------
Key: MCOMPILER-388 (was: MTOOLCHAINS-30)
Project: Maven Compiler Plugin (was: Maven Toolchains Plugin)
> Certain errors appearing at the end of error stream are not parsed and
> displayed
> --------------------------------------------------------------------------------
>
> Key: MCOMPILER-388
> URL: https://issues.apache.org/jira/browse/MCOMPILER-388
> Project: Maven Compiler Plugin
> Issue Type: Bug
> Reporter: James Gough
> Priority: Major
>
> Whilst investigating [MTOOLCHAINS-19] I came across a bug where certain
> errors are not parsed and displayed to the user, the specific example is when
> the compiler has an error for an access/bad source file.
> Using git bisect I found the issue to be related to the upgrade of the
> plexus-compiler:
> {code:bash}
> commit db6050f06e22065f7687ae0c7cda616e4183a9b8
> Author: Robert Scholte <rfscho...@apache.org>
> Date: Sun Jun 26 14:33:13 2016 +0000
> [MCOMPILER-269] Support modulepath (Java9/Jigsaw)
> [MCOMPILER-270] Support release=8 on JDK 9 (with fallback on source=8 and
> target=8 on JDK 8)
> Upgrade plexus-compiler to 2.8
> {code}
> The issue only seems to manifest during a compile out of process compilation,
> which then relies on parsing the output of the forked process.
> I have provide a merged bug fix to the plexus-compiler project
> https://github.com/codehaus-plexus/plexus-compiler/pull/63 that fixes the
> issue.
> To fix this bug in the maven-compiler we will need to use the above fix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
