maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Fortescue (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCOMPILER-62) Allow multiple options to be passed to compiler for options not supported by the compiler mojo
Date Thu, 23 Dec 2010 17:14:58 GMT

    [ http://jira.codehaus.org/browse/MCOMPILER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249571#action_249571
] 

Nick Fortescue commented on MCOMPILER-62:
-----------------------------------------

Is there any chance this patch could be incorporated? It seems to solve all the issues with
a nice design, and has been around for 3 years. It also resolves the problems with MCOMPILER-135.
I can't see any downside to it. It won't break any existing pom files.

> 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

        

Mime
View raw message