You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mike Perham (JIRA)" <ji...@codehaus.org> on 2006/01/19 16:19:40 UTC
[jira] Created: (MCLOVER-19) Document clover build integration
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
[jira] Commented: (MCLOVER-19) Separate report generation &
database generation
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56469 ]
Mike Perham commented on MCLOVER-19:
------------------------------------
Vincent, I just started work on implementing this. Would you like me to hold off?
> 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
[jira] Commented: (MCLOVER-19) Document clover build integration
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MCLOVER-19) Separate report generation & database
generation
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MCLOVER-19) Document clover build integration
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCLOVER-19) Separate report generation &
database generation
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56472 ]
Vincent Massol commented on MCLOVER-19:
---------------------------------------
oh ok. I misunderstood. I didn't realize you wanted to implement it! That's cool with me :-)
> 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
[jira] Commented: (MCLOVER-19) Document clover build integration
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56465 ]
Vincent Massol commented on MCLOVER-19:
---------------------------------------
"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."
I definitely agree. Could you please open a JIRA issue for this? Or should we change the summary of this issue? "Document clover build integration" doesn't seem right. I don't think it's a problem of documentation... It has to be implemented...
Thanks
> 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
> 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
[jira] Updated: (MCLOVER-19) Enable clover build integration
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=all ]
Mike Perham updated MCLOVER-19:
-------------------------------
Summary: Enable clover build integration (was: Document clover build integration)
I wasn't sure if it was a feature that wasn't documented or just not possible. Now that I know it is not possible, "Document" -> "Enable".
> Enable 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
> 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
[jira] Commented: (MCLOVER-19) Separate report generation &
database generation
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56478 ]
Vincent Massol commented on MCLOVER-19:
---------------------------------------
Mike, I'm now watching but I don't have too much time right now. I'll try to help you over the week end but I'm awfully busy with other stuff...
> 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
[jira] Commented: (MCLOVER-19) Separate report generation &
database generation
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MCLOVER-19) Separate report generation &
database generation
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-19?page=comments#action_56475 ]
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\BaseAdminImpl.java: Double instrumentation detected: D:\perforce\depot\modules\cordoba\client\api\target\clover\src\com\webify\wsf\client\BaseAdminImpl.java 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: http://jira.codehaus.org/browse/MCLOVER-19
> 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 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