maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MCOMPILER-16) ability to separate compilation parameters for different compilers / create a compilation configuration object
Date Sun, 06 Sep 2015 20:51:48 GMT

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

Michael Osipov closed MCOMPILER-16.
-----------------------------------
    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.

> ability to separate compilation parameters for different compilers / create a compilation
configuration object
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-16
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-16
>             Project: Maven Compiler Plugin
>          Issue Type: Bug
>            Reporter: Brett Porter
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message