[ 
https://issues.apache.org/jira/browse/LUCENE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487052#comment-14487052
 ] 

Uwe Schindler commented on LUCENE-5439:
---------------------------------------

Hi Robert,
very cool. I had the same idea for clover a while back to have separate 
databases per thread, but i gave up, because clover has no merging 
functionality (at least I did not understand how to use it). Also the setup of 
clover in lucene was to have a one-for-all clover database...

I checked you patch, very minimal invasive, cool! Just a few test policy files 
and the "hack" with relative paths for the database. I just wonder why the 
"clover" target is sometimes included as dependency to the new tasks, but maybe 
thats just copypaste.

A further imprvement could be to have a root-level report with lucene+solr for 
Jenkins. Should be easy. Maybe make the report generator a macro in 
common-build.

I still like the clover reports more (they have much nicer report output and 
functionality), but jacoco is fast and - as Grant said - does not need to 
istrument classes at compile time. So you can quickly switch between jacoco and 
non-jacoco without recompiling (for Clover you had to "ant clean" first).

+1 to start with this. Maybe we can remove the invasive clover at some time - 
but not under the scope of that issue! :-)

> Add Jacoco option for Test Coverage
> -----------------------------------
>
>                 Key: LUCENE-5439
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5439
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Robert Muir
>            Priority: Minor
>         Attachments: LUCENE-5439.patch, LUCENE-5439.patch, LUCENE-5439.patch
>
>
> Jacoco (http://www.jacoco.org/) is a much cleaner and simpler to use code 
> coverage tool than clover and additionally doesn't require having a third 
> party license since it is open source.  It also has nice Jenkins integration 
> tools that make it incredibly easy to see what is and isn't tested.  We 
> should convert the Lucene and Solr builds to use Jacoco instead of Clover.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to