You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Vaynberg (JIRA)" <ji...@codehaus.org> on 2009/11/08 08:14:55 UTC
[jira] Updated: (MCOMPILER-62) Allow multiple options to be passed
to compiler for options not supported by the compiler mojo
[ http://jira.codehaus.org/browse/MCOMPILER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated MCOMPILER-62:
-----------------------------------
Attachment: MCOMPILER-62.patch
a patch for the <compilerArgument> value not working propery. currently the entire value is used as a simple parameter, i think all that needs to happen is that the value needs to be splint on whitespace and each part added as a separate argument. this is what the patch does.
a more robust version may handle <cr> <lf> just in case.
> Allow multiple options to be passed to compiler for options not supported by the compiler mojo
> ----------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-62
> URL: http://jira.codehaus.org/browse/MCOMPILER-62
> Project: Maven 2.x Compiler Plugin
> Issue Type: Improvement
> Environment: Maven version: 2.0.7
> Reporter: Sanjeeb Sahoo
> Attachments: 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira