[
https://jira.codehaus.org/browse/MCOMPILER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Schaible closed MCOMPILER-201.
-----------------------------------
Resolution: Not A Bug
The problem is a result of the new behavior in version 3.0 to use the tools.jar
of the JDK instead of the native compiler. The usage of javac can now be forced
with the new option forceJavacCompilerUse, which allows the IT to pass.
> [Regression] Compilation fails due to ignored compiler argument
> ---------------------------------------------------------------
>
> Key: MCOMPILER-201
> URL: https://jira.codehaus.org/browse/MCOMPILER-201
> Project: Maven 2.x Compiler Plugin
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Jörg Schaible
> Attachments: compilerArgs-it.tb2
>
>
> With compiler plugin 2.5.1 we can configure the Sun/Oracle compiler with
> {noformat}
> <compilerArguments>
> <XDignore.symbol.file />
> </compilerArguments>
> {noformat}
> to support internal classes, in our case constants from
> com.sun.xml.internal.ws.developer.JAXWSProperties.
> Since compiler version 3.0, the compilation fails, the symbol is no longer
> found. Same for the upcoming 3.1 in the stage area even if we use the new
> configuration syntax:
> {noformat}
> <compilerArgs>
> <compilerArg>-XDignore.symbol.file</compilerArg>
> </compilerArgs>
> {noformat}
> Since we can see with Maven's debug output that the argument is formally
> detected, the bug could be actually a problem of the newer plexus-compiler
> dependencies (1.9.1 vs. 2.0).
> IT attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
