[ http://jira.codehaus.org/browse/MCLOVER-19?page=all ]
Vincent Massol updated MCLOVER-19:
----------------------------------
Assign To: Vincent Massol (was: Mike Perham)
Summary: Separate report generation & database generation (was: Enable
clover build integration)
> Separate report generation & database generation
> ------------------------------------------------
>
> Key: MCLOVER-19
> URL: http://jira.codehaus.org/browse/MCLOVER-19
> Project: Maven 2.x Clover Plugin
> Type: Improvement
> Versions: 2.0
> Reporter: Mike Perham
> Assignee: Vincent Massol
> Fix For: 2.1
>
>
> From my email to the user list:
> How do we get the Clover report to generate as part of the normal build?
> If I run 'mvn clover:clover' it generates the report but does not perform the
> install process.
> If I run 'mvn site:site' with the clover report plugin, same as clover:clover.
> If I run 'mvn install site:site', it builds the project twice.
> Is there a way to get the clover database generated from the normal build
> lifecycle and the site report to use that pre-generated database so it does
> not have to build twice? My projects cannot build twice in a row - they
> assume a clean build every time. The HowTo does not cover this usecase but
> it seems pretty common to want the daily build to create the artifacts AND
> document the status of your unit tests.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
