Scoverage Sensor not honouring property sonar.projectBaseDir about sbt-sonar

[BalmungSan]

Hello @gheo21, by chance are you running the analysis from a Wiindows machine ?

[gheo21]

Hello,

@BalmungSan no, it 's a macOs. I've already checked the other items related to the test coverage not being shown, but I couldn't find a fix it.

Thanks!

[mwz]

Thanks for reporting this issue @gheo21. It is interesting and before I do any digging I was wondering if you had a chance to check the following:

• does this only affect the Scoverage sensor or Scalastyle and/or Scapegoat too?
• are you seeing the same behaviour when executing the analysis using the bare sonar-scanner?

Just as a sidenote, from my understanding of how the projectBaseDir property works, if you set it sonar will no longer run analysis on your aggregate project, but I can be wrong about this.

[gheo21]

Hello @mwz,

Thanks for getting back to me.

1. It looks like the other plugins are not affected by this.
2. It works if I execute the sonnar-scanner, though not using the projectBaseDir

unzip multi-module-new.zip
cd multi-module-new/modules
$SONAR_SCANNER_HOME/bin/sonar-scanner -Dsonar.modules=module1,module2 -Dsonar.host.url=http://localhost:80 -Dsonar.projectKey=module1 -Dmodule1.sonar.sources=src/main/scala -Dmodule2.sonar.sources=src/main/scala -Dsonar.scala.scoverage.reportPath=target/scala-2.12/scoverage-report/scoverage.xml

So as an intermediate solution I will go with option two, but I think this should work with the sonar scanner sbt plugin.

Best regards!

[mwz]

Ok, if other plugins are not affected by this, then it's probably got something to do with the way sonar-scala matches paths in the Scoverage reports. I'll have a look into this when I get a minute.