You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (Jira)" <ji...@apache.org> on 2020/09/29 19:33:00 UTC

[jira] [Commented] (SLING-9775) Improve JaCoCo code coverage setup

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

Radu Cotescu commented on SLING-9775:
-------------------------------------

This issue, together with the improvements from SLING-8995, should help report the correct coverage measurements once the Sling modules update to a parent pom >= 40.

> Improve JaCoCo code coverage setup
> ----------------------------------
>
>                 Key: SLING-9775
>                 URL: https://issues.apache.org/jira/browse/SLING-9775
>             Project: Sling
>          Issue Type: Improvement
>          Components: Build and Source Control
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Parent 40, Bundle Parent 40
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> While the parent pom defines a good setup for the JaCoCo Maven Plugin, the integration with JaCoCo - configurations for the {{surefire}} and {{failsafe}} plugins - has to be performed in each project using the parent pom. This leads to inconsistent configurations and sometimes not all coverage is correctly reported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)