You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Steinar Bang (JIRA)" <ji...@apache.org> on 2019/01/26 14:09:00 UTC
[jira] [Created] (SUREFIRE-1630) sonarqube reports 0% coverage with
maven-surefire-plugin versions later than 2.20
Steinar Bang created SUREFIRE-1630:
--------------------------------------
Summary: sonarqube reports 0% coverage with maven-surefire-plugin versions later than 2.20
Key: SUREFIRE-1630
URL: https://issues.apache.org/jira/browse/SUREFIRE-1630
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.22.1, 2.22.0, 2.21.0, 2.20.1
Environment: Debian 9.7 "stretch", amd64, openjdk-8 8u181-b13-2~deb9u1, maven 3.3.9-4, JUnit 5.1.0
Reporter: Steinar Bang
I create sonar reports with the following command line and no sonar or jacoco config in my POMS:
{noformat}
mvn clean org.jacoco:jacoco-maven-plugin:prepare-agent install sonar:sonar
{noformat}
With maven surefire plugin 2.x versions newer than 2.20 the resulting sonar report shows 0% test coverage.
My workaround to get coverage back, was to downgrade to surefire 2.20.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)