[
https://jira.codehaus.org/browse/MCOMPILER-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy updated MCOMPILER-192:
-----------------------------------
Summary: No error reporting with forked compiler when Compiler includes non
java files (was: Compiler includes non java files)
> No error reporting with forked compiler when Compiler includes non java files
> -----------------------------------------------------------------------------
>
> Key: MCOMPILER-192
> URL: https://jira.codehaus.org/browse/MCOMPILER-192
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Environment: Windows 7
> Reporter: Trevor Baker
> Attachments: test2.zip
>
>
> I notice one of my builds had this in the maven-compiler-plugin configuration:
> {noformat}
> <include>my/path/MyFile.inc</include>
> {noformat}
> In 2.5.1, the inc file is excluded from the generated compiler file and the
> build is successful.
> In 3.0, the inc file is included in the generated compiler file and the build
> is not successful. There are no warnings or errors displayed.
> The CLI returnCode is 2 but there is no output to grab messages from. When I
> grab the generated compiler file and run by myself on the command line, I get
> this:
> {noformat}
> $ cmd.exe /X /C "C:\tools\jdk-1.6.0_33\bin\javac.exe
> @C:/Tools/cygwin/tmp/org.codehaus.plexus.compiler.javac.JavacCompiler3357522045371592375arguments"
> javac: invalid flag: C:/Users/me/project/src/java/my/path/MyFile.inc
> Usage: javac <options> <source files>
> use -help for a list of possible options
> {noformat}
> I've removed the inc file from the compiler configuration, but the compiler
> plugin should handle more gracefully.
--
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
