maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCLOVER-19) Document clover build integration
Date Fri, 20 Jan 2006 15:43:06 GMT
    [ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56459 ] 

Vincent Massol commented on MCLOVER-19:
---------------------------------------

I'm not sure what you mean "does not perform the install process". Do you mean that the install
phase is not called? That would be normal since you didn't call it ;-)

Right now the use case you mention is not implemented (but almost there) and I agree it's
a common one that I have also identified. I'm planning to work on it but it'll take me some
time (say 2 weeks) because I'm busy on other things.

If clover:clover works for you then you can simply add it to your pom.xml in an execution
and bind it whatever phase you want (like the package one for example or the integration-test
one).

That said, generating a report is not meant to be part of the main build. it's meant to be
part of the site build which is why it gets generated when you run site:site.

It's the same as if you were saying that you want the project information plugin to generate
reports when you run "mvn install". It's not the way it works. These information are meant
to be generated by the site lifeyccle, not the main build lifecycle.

clover:check is another matter though and this goal is meant to be executed during the main
build lifecycle.

hmm... (more thinking)....

There might be a way to reconcile all this but it's not implemented yet. We could consider
that the clover plugin generates an artifact which is the clover database. The only issue
is that thee are several files to they would probably need to be zipped all together. In any
case, I think this is a direction to explore if we want a subproject (aka module) to be able
to add to an existing clover database without relying on the file system.

If we had this then the site lifecycle would simply generate a report out of a clover database
without running insturmentation, compilation, etc.





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


Mime
View raw message