[
https://jira.codehaus.org/browse/MCOMPILER-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=313211#comment-313211
]
Anders Hammar edited comment on MCOMPILER-160 at 11/8/12 2:48 PM:
------------------------------------------------------------------
The rework in the upcoming plexus-compiler:2.0 should solve this as there is
now a separate success flag returned which is based on the actual return code
from the compiler.
@Jochen: Could you please test 3.0-SNAPSHOT of maven-compiler-plugin on a
problematic project?
was (Author: afloom):
The rework in the upcoming plexus-compiler:2.0 should solve this as there
is now a separate success flag returned which is based on the actual return
code from the compiler.
@Jochen: Could you please test 3.0-SNAPSHOT of maven-compiler-test on a
problematic project?
> 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
> Assignee: Anders Hammar
> Priority: Critical
> Fix For: 3.0
>
>
> 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
