maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Perham (JIRA)" <>
Subject [jira] Commented: (MCLOVER-19) Separate report generation & database generation
Date Fri, 20 Jan 2006 18:09:06 GMT
    [ ] 

Mike Perham commented on MCLOVER-19:

So I created a CloverCloverMojo which extends CloverReportMojo.  The latter has no execute
annotation while the former has no code, just extends CloverReport and defines an execute
annotation.  I hooked up my parent POM to enable instrument during the generate-sources phase.

1) When I run 'mvn install site:site', the reporting subsystem appears to scan for MavenReport
instances and runs them all... including CloverCloverMojo, which runs the extra lifecycle
and I get this error:

ERROR: Error parsing D:\perforce\depot\modules\cordoba\client\api\target\clover\src\com\webify\wsf\client\
Double instrumentation detected: D:\perforce\depot\modules\cordoba\client\api\target\clover\src\com\webify\wsf\client\
appears to have already been instrumented by Clover.

Is there a way to make a report standalone so it does not run when generating the site?

> Separate report generation & database generation
> ------------------------------------------------
>          Key: MCLOVER-19
>          URL:
>      Project: Maven 2.x Clover Plugin
>         Type: Improvement

>     Versions: 2.0
>     Reporter: Mike Perham
>     Assignee: 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
> 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:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message