[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56463 ]
Mike Perham commented on MCLOVER-19: ------------------------------------ I think you understood my usecase but I will restate it in case something was not clear. My build runs 'mvn install site:site' on every module. I want clover instrumentation to be integrated into the build lifecycle i.e. 'mvn install'. I can't use clover:clover hooked into package because it causes the build to be run a second time. Ideally I could hook clover:instrument into an early build phase and the database would be generated when the tests are run. Then when site:site is executed, it would detect the existing clover database from the build and use it to generate the report. The problem as I see it is that the report generation is intimately tied to a forked build execution rather than simply depending on a pre-generated database. It seems like CloverReportMojo could be broken into two goals, one being a really simple goal to use an existing database and a second which acts like the current clover:clover goal. Multi-module aggregation of the database is not important to me at this point. > Document clover build integration > --------------------------------- > > 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 > 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]
