Will sonar.jacoco.reportPaths work in Sonar 7 LTS?

SonarQube Server / Community Build
, ,
1

Hi Sonar Team!

I have several related questions on the support for Jacoco support. For a short historical overview:

The oldest solution was the separated properties of sonar.jacoco.reportPath, sonar.jacoco.itReportPath . These should not be used at all. sonar.jacoco.reportPaths (notice the ‘s’) is a trivial upgrade. This property is described both in the online docs, and also for the configuration page of the Java plugin inside the server. (assuming latest available versions)

Question 1:
sonar.jacoco.reportPaths is deprecated already. Does this mean it will not work at all in the soon-to-come Sonar 7 LTS version? Or will it still work, alongside with a visible warning on the project analysis page? Instead of that deprecated property supporting exec format, the new property for XML format is already suggested: sonar.coverage.jacoco.xmlReportPaths
some more comments on this Jacoco coverage reporting differently in Sonarcloud

Question 2:
Shouldn’t sonar.coverage.jacoco.xmlReportPaths be represented in the Sonar server configuraiton menu?

Environment:
SonarQube 7.7
SonarJava 5.12.1
SonarJacoco 1.0.1

I expect the new XML property to be configurable ( and anyway mentioned) from the configuration screen: Adminstration -> Configuration -> Java -> JaCoCo
Only the exec property is mentioned which is somewhat confusing.

Thanks a lot and cheers,
Balázs

1 Like
3

Hello,

Question 1:
Yes, sonar.jacoco.reportPaths will continue to work with SonarQube 7.9 LTS with a WARN in the UI to incite users to move to sonar.coverage.jacoco.xmlReportPaths.

Then at some point in time in 2019 (the initial plan is Sept 2019), SonarJava will stop supporting sonar.jacoco.reportPaths and loading of JaCoCo will be only possible thru the XML format.
So it’s when you will upgrade SonarJava around Sept 2019 on your SonarQube 7.9 LTS that you will potentially see the impact (no coverage visible) if you did not migrate yet to the XML format.

See https://jira.sonarsource.com/browse/MMF-1651 and https://jira.sonarsource.com/browse/MMF-1362 for the related specifications.

Question 2:
Fair point, I created https://jira.sonarsource.com/browse/JACOCO-8 to fix this.

Regards

1 Like