Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: 
 <116022922.1137781279396.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Fri, 20 Jan 2006 12:21:19 -0600 (CST)
From: "Mike Perham (JIRA)" <jira@codehaus.org>
To: dev@maven.apache.org
Subject: [jira] Commented: (MCLOVER-19) Separate report generation &
 database generation
In-Reply-To: 
 <99538563.1137683980449.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

    [ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56480 ] 

Mike Perham commented on MCLOVER-19:
------------------------------------

No problem, I'm about tapped out for Maven time today also so an immediate response to unblock me is not needed.

Next problem: the build packages the Clover-modifed classes in the jar so the code fails to work at runtime.  The unit tests should use the Clover-modified classes but the build should package the standard classes.

Hmmm, this is looking more and more non-trivial.

> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org