[
https://jira.codehaus.org/browse/MCOMPILER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311105#comment-311105
]
Anders Hammar commented on MCOMPILER-160:
-----------------------------------------
Just sent a pull request on plexus-compiler
(https://github.com/sonatype/plexus-compiler/pull/7) that contains a fix of the
existing band-aid catching mechanism of unparseable errors. This ensure that
the scenario described in this ticket shouldn't happen I believe (at least it
solves the scenario I ran into).
plexus-compiler-javac should handle this better (logging wise) but this will at
least prevent m-compiler-p from incorrectly reporting compilation as successful.
Could someone with commit rights for plexus-compiler take a look please?
> javac error but build SUCCESS
> -----------------------------
>
> Key: MCOMPILER-160
> URL: https://jira.codehaus.org/browse/MCOMPILER-160
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 2.3.2
> Environment: Java 1.6.0_25
> Reporter: Jochen Stiepel
> Priority: Critical
>
> Using javac as the (default)compiler for my source files no classes are
> generated, but the Maven Build says build "SUCCESS".
> Using "tycho-compiler-jdt" as the compiler, the class files are generated
> correctly.
> reproducible = always.
> Using -X show's the javac compiler commandline, but it is to long (108376
> char's) to execute it from the cmd on windows.
> Can I provide more information?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
