You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2006/04/04 11:03:48 UTC
[jira] Created: (MCLOVER-32) Add support for aggregating functional
tests results
Add support for aggregating functional tests results
----------------------------------------------------
Key: MCLOVER-32
URL: http://jira.codehaus.org/browse/MCLOVER-32
Project: Maven 2.x Clover Plugin
Type: Task
Versions: 2.0
Reporter: Vincent Massol
Assigned to: Vincent Massol
In order to aggregate functional tests we need to do the following:
* Modify clover:instrument so that the forked lifecycle extends till the install phase
* Create an internal clover mojo bound to the install phase that will created a clovered version of the project's artifact as an attached artifact (classifier = "clover").
* Handle the different type of packaging. For example for a WAR packaging, add the clover jar to the attached clovered WAR, etc.
* Modify the clover:instrumentInternal so that for any dependency artifact, it looks for the clovered version in the repo and adds it instead of the non-clovered version.
Quite some work...
The Clover plugin is bound to become the most complex m2 plugin ever written! :-)
--
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
[jira] Closed: (MCLOVER-32) Add support for aggregating functional
tests results
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-32?page=all ]
Vincent Massol closed MCLOVER-32:
---------------------------------
Resolution: Fixed
Fix Version: 2.1
Done
> Add support for aggregating functional tests results
> ----------------------------------------------------
>
> Key: MCLOVER-32
> URL: http://jira.codehaus.org/browse/MCLOVER-32
> Project: Maven 2.x Clover Plugin
> Type: Task
> Versions: 2.0
> Reporter: Vincent Massol
> Assignee: Vincent Massol
> Fix For: 2.1
>
>
> In order to aggregate functional tests we need to do the following:
> * Modify clover:instrument so that the forked lifecycle extends till the install phase
> * Create an internal clover mojo bound to the install phase that will created a clovered version of the project's artifact as an attached artifact (classifier = "clover").
> * Handle the different type of packaging. For example for a WAR packaging, add the clover jar to the attached clovered WAR, etc.
> * Modify the clover:instrumentInternal so that for any dependency artifact, it looks for the clovered version in the repo and adds it instead of the non-clovered version.
> Quite some work...
> The Clover plugin is bound to become the most complex m2 plugin ever written! :-)
--
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