[
https://issues.apache.org/jira/browse/JCR-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated JCR-5174:
---------------------------------
Fix Version/s: 2.24
2.23.3
Resolution: Fixed
Status: Resolved (was: Patch Available)
Fixed in
https://github.com/apache/jackrabbit/commit/65fd0fa2ec9a5ffeac56e2b1b931a0a263f0a9f5
and
https://github.com/apache/jackrabbit/commit/49a1bbf93668a3394f44ce611d06637f257f132e.
> Exclude jackrabbit-jcr-tests from coverage calculation
> ------------------------------------------------------
>
> Key: JCR-5174
> URL: https://issues.apache.org/jira/browse/JCR-5174
> Project: Jackrabbit Content Repository
> Issue Type: Sub-task
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 2.24, 2.23.3
>
>
> Although https://github.com/apache/jackrabbit/tree/trunk/jackrabbit-jcr-tests
> contains only tests SonarQube treats them as regular code (as the source is
> contained in {{src/main/java}} in order to depend on it in downstream
> modules). One should exclude it from coverage calculation
> (https://docs.sonarsource.com/sonarqube-server/latest/instance-administration/analysis-functions/analysis-scope/exclude-from-coverage-duplication/).
> Unfortunately the Jacoco exclusions are not considered by SonarQube (i.e.
> files excluded in Jacoco still appear as having 0 coverage in SonarQube):
> https://groups.google.com/g/sonarqube/c/VwEE_ZD2KzI
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
