[
http://jira.codehaus.org/browse/MNG-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107088
]
Brett Porter commented on MNG-3203:
-----------------------------------
I'm not sure what you mean here - how would this be used? Maybe something like:
<configuration>
<shared>...</shared>
</configuration>
<executions>
<execution>
<id>testCompile</id>
<configuration>
<something>...
</configuration>
<!-- not goals, that's already bound -->
</execution>
</executions>
I'm not even sure that'd work - could be a good way to achieve this though.
Would you implement it by putting every bound goal in it's own execution?
Currently, there is no way to specify this in the default lifecycles.
> maven should execute compiler:compile and :test-compile in separate
> executions, to allow separate configuration
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MNG-3203
> URL: http://jira.codehaus.org/browse/MNG-3203
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.7
> Reporter: John Casey
> Fix For: 2.0.8, 2.1-alpha-1
>
>
> Currently, it's impossible to configure the two default maven-compiler-plugin
> mojos in the jar lifecycle (:compile and :test-compile) separately without
> the configuration for one affecting both. This is because they are both
> executed in the same (default) execution. We should be assigning these to
> different execution id's, to allow separate configuration.
--
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
