Hi,
Yes, it seems to be. That’s quite strange. Thank you for all of your help Colin
Hi,
Yes, it seems to be. That’s quite strange. Thank you for all of your help Colin
Actually @Colin could it have to do with my sonar configuration? In my dashboard it just starts at src/main/java
rather than another level above and my config is as follows property "sonar.sources", "src/main/java"
. Should that config be altered? Or how did you configure sonar
in the playground app you cloned?
As a result of this, I don’t think I’m getting a true reflection in sonar cloud of the code coverage (as in the module coverage is missing)
I didn’t alter any configuration (like adding sonar.sources
) as the Scanner for Gradle has a lot of analysis defaults that derive things like sonar.sources
from the build.
How about you try removing this configuration all together?
property "sonar.java.coveragePlugin", "jacoco"
....
property "sonar.sources", ["src/test", "src/main/java"]
property "sonar.tests", "src/test"
property "sonar.test.inclusions", "**/*Test*/**"
....
property "sonar.sources", "src/main/java"
property "sonar.java.coveragePlugin", "jacoco"
These analysis parameters either don’t exist anymore, or have sound defaults set by the scanner for gradle
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.