[
https://jira.codehaus.org/browse/MCOMPILER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311186#comment-311186
]
Anders Hammar commented on MCOMPILER-160:
-----------------------------------------
For the record, I can't figure out how to write an integration test for this
one as the root cause is an error message which can't be parsed correctly (for
example an exception/bug in the compiler) in combination with some warning
messages which are parsed correctly.
Don't know how to force an exception in the compiler which would be compiler
and compiler version neutral (as well as platform neutral).
> 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
