You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2014/07/02 15:45:17 UTC

[jira] (MNG-474) performance improvement for forked lifecycles

     [ https://jira.codehaus.org/browse/MNG-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict updated MNG-474:
------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> performance improvement for forked lifecycles
> ---------------------------------------------
>
>                 Key: MNG-474
>                 URL: https://jira.codehaus.org/browse/MNG-474
>             Project: Maven
>          Issue Type: Improvement
>          Components: Design, Patterns & Best Practices, Performance, Plugins and Lifecycle
>            Reporter: Brett Porter
>
> look into a way to avoid rerunning some heavy goals again unnecessarily.
> For example, currently clover:check run after test will execute the tests again with clovered classes. It would be nice to fold that down onto the same lifecycle when it is known not to be harmful to the existing parts, but also keep it separate enough that packing won't include clovered classes, for example.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)