[
https://issues.apache.org/jira/browse/MCOMPILER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MCOMPILER-62.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow multiple options to be passed to compiler for options not supported by
> the compiler mojo
> ----------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-62
> URL: https://issues.apache.org/jira/browse/MCOMPILER-62
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Environment: Maven version: 2.0.7
> Reporter: Sahoo
> Attachments: MCOMPILER-62-2.3.2.patch, MCOMPILER-62-2.3.2.patch,
> MCOMPILER-62.patch
>
>
> Look at the mail thread in maven user group:
> http://www.nabble.com/Not-able-to-pass-multiple-arguments-to-javac-tf4857909s177.html
> User may have to pass options to the underlying compiler that are not yet
> supported by the mojo. Current implementation of the maven-compiler-plugin
> allows user to specify only one option. Neither of the following techniques
> work:
> <configuration>
> <compilerArgument>-proc:none</compilerArgument>
> <compilerArgument>-implicit</compilerArgument>
> </configuration>
> or
> <configuration>
> <compilerArgument>-proc:none -impicit</compilerArgument>
> </configuration>
> In the first approach, only one of the compilerArgument is considered, in the
> second approach since maven quotes the argument, it ends up as a single
> argument to javac and hence becomes an invalid option.
> The best suggestion is to allow multiple compilerArgument -- may be something
> like:
> <compilerArguments>
> <compilerArgument/>
> <compilerArgument/>
> </compilerArguments>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
