You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/31 15:22:55 UTC

[jira] Reopened: (MCOMPILER-15) ability to have different test compilation parameters to general compilation parameters

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

Benjamin Bentmann reopened MCOMPILER-15:
----------------------------------------


> ability to have different test compilation parameters to general compilation parameters
> ---------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-15
>                 URL: http://jira.codehaus.org/browse/MCOMPILER-15
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>            Reporter: Brett Porter
>
> when we stopped doing per goal compilation because of its verbosity, we decided anything that had a different meaning in different mojos within a plugin would need a different parameter name. The compiler plugin slipped through this - specifically the compilation parameters for tests.
> What we probably want is to be able to specify the test parameters separately, defaulting to the normal compilation parameters, and then the general defaults.
> I think this should depend on us first splitting the compilation parameters into a separate component however so that they can be different depending on whether it is a java compiler, c# compiler, etc.

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