Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-3295

Change sonar.jacoco.excludes behaviour so that it excludes from both instrumentation and coverage report

    XMLWordPrintable

    Details

      Description

      Hi there, we want to switch from clover code coverage to jacoco. There is a couple of projects that exclude classes from code coverage, but we still run rules on them for violations. I tried using sonar.jacoco.excludes but instead of excluding that code for coverage, it just assigns 0% to them so that it lowers the coverage numbers for their components. I can't understand the logic of this. Shouldn't it exclude those classes from instrumentation AND the coverage report like clover and cobertura excludes? It would be great to change this behavior instead of waiting for SONAR-766 to be addressed.

      Thanks,
      Scott

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              godin OLD - Evgeny Mandrikov
              Reporter:
              swolk Scott Wolk
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: