You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/15 05:09:06 UTC
[jira] Created: (MNG-1566) ability to separate compilation parameters for different compilers / create a compilation configuration object
ability to separate compilation parameters for different compilers / create a compilation configuration object
--------------------------------------------------------------------------------------------------------------
Key: MNG-1566
URL: http://jira.codehaus.org/browse/MNG-1566
Project: Maven 2
Type: Improvement
Components: maven-compiler-plugin
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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MCOMPILER-16) ability to separate compilation
parameters for different compilers / create a compilation configuration
object
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-16?page=all ]
Carlos Sanchez updated MCOMPILER-16:
------------------------------------
Fix Version: 2.1
> 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
> Type: Bug
> Reporter: Brett Porter
> Fix For: 2.1
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org