[
https://issues.apache.org/jira/browse/LUCENE-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487254#comment-14487254
]
Uwe Schindler commented on LUCENE-5439:
---------------------------------------
This is what root's build.xml contains:
{noformat}
<!-- The idea behind Clover is to determine test coverage, so be immune
to failing tests: -->
<param name="tests.haltonfailure" value="false"/>
{noformat}
If we do the same there is no problem to *also* generate a combined coverage
report for Jenkins. Users can still generate reports as they like for
sub-modules. I will open another issue about that.
> 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
> Fix For: Trunk, 5.2
>
> 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]
