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/06/16 09:27:26 UTC
[jira] Created: (MNG-474) performance improvement for forked lifecycles
performance improvement for forked lifecycles
---------------------------------------------
Key: MNG-474
URL: http://jira.codehaus.org/browse/MNG-474
Project: Maven 2
Type: Improvement
Components: maven-core
Reporter: Brett Porter
Fix For: 2.1-beta-1
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 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: (MNG-474) performance improvement for forked
lifecycles
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-474?page=all ]
Jason van Zyl updated MNG-474:
------------------------------
Component: (was: Plugins and Lifecycle)
Performance
> performance improvement for forked lifecycles
> ---------------------------------------------
>
> Key: MNG-474
> URL: http://jira.codehaus.org/browse/MNG-474
> Project: Maven 2
> Type: Improvement
> Components: Performance
> Reporter: Brett Porter
> Fix For: 2.1
>
>
> 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 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: (MNG-474) performance improvement for forked
lifecycles
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-474?page=all ]
Brett Porter updated MNG-474:
-----------------------------
Component: Plugins and Lifecycle
Design & Best Practices
> performance improvement for forked lifecycles
> ---------------------------------------------
>
> Key: MNG-474
> URL: http://jira.codehaus.org/browse/MNG-474
> Project: Maven 2
> Type: Improvement
> Components: Plugins and Lifecycle, Design & Best Practices, Performance
> Reporter: Brett Porter
> Fix For: 2.1
>
>
> 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 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