[jira] Updated: (MCOMPILER-16) ability to separate compilation parameters for different compilers / create a compilation configuration object

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MCOMPILER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MCOMPILER-16:
--------------------------------

    Fix Version/s:     (was: 2.2)
                   2.3

> ability to separate compilation parameters for different compilers / create a compilation configuration object
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-16
>                 URL: http://jira.codehaus.org/browse/MCOMPILER-16
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>            Reporter: Brett Porter
>             Fix For: 2.3
>
>
> I think we should introduce a compilation configuration object (and deprecate but not remove the old parameters) in the compiler plugin. This can have a base class that is extended by the different compiler types.
> I'm not sure if the Maven processing does enough just yet to be able to set a specific field with the right type without setting implementation="" however, and we should also be able to make the object a fullly-fledged component (with expressions and default values, as long as it is in the same source tree).

-- 
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