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

Robert Muir commented on LUCENE-5439:
-------------------------------------

{quote}
I just wonder why the "clover" target is sometimes included as dependency to 
the new tasks, but maybe thats just copypaste.
{quote}

No copypaste. Because tests may fail if you do not. this target initializes 
stuff even for the case where clover is not used! So it must be called. Seems 
like clover integration should be cleaned up a bit here.

{quote}
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.
{quote}

I don't want this. I am tired of not having a code coverage report in jenkins 
for lucene for months, and its because solr tests fail! Nobody wants to make 
solr tests reliable, so fine, i will make code coverage separate so that we 
have it again for lucene. That is why i worked on this issue, so that lucene 
will have code coverage again.



> 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