Can't find source folder about sbt-sonar

[ricardoatsouza]

Adding .settings(aggregate in sonarScan := false) does the job. Thanks. 👍

[mwz]

It looks all good on my end... I think your problem might be related to how you configured the project in your build.sbt. Also, you want sonnarScan to be run only once for your root project, so you need to exclude the task from the aggregation by setting aggregate in sonarScan to false.
I just added an example multi-module project, which you can use as a reference 47126c4.

[ricardoatsouza]

Hi @mwz , thanks for the answer.
I'm also almost 100% convinced that this looks like a misconfiguration.

The annoying think is that I don't know where it is. Looking at the documentation, everything seems to be fine (well... we know how that goes :D ). So, if you have any ideas of where I should look into, let me know.

Thanks

[ricardoatsouza]

Just to report it here.

I created a new jar file from the master branch for the Scala plugin I'm using (Sagacify/sonar-scala) and updated it in Sonarqube. But, still, the property <sub-project>.sonar.scoverage.reportPath were needed to be defined manually.

If this is a issue in the plugin, or a misconfiguration on my side, it's still unclear. But since I did this small investigation, it's nice to report it here, so others might find this useful.

@mwz Thanks for the help! This issue can be happily closed. :)

[ricardoatsouza]

Btw, using Scala 2.12.3, SonarQube 6.7.1, and Sbt-sonar 1.3.0.

[mwz]

Hi @ricardoatsouza, thanks for the shout - I'll have a look. I've used sonar with multi-module projects without any issues in the past, so it might be just a misconfiguration.
I was planning to add a multi-module example to sbt tests, so this is a perfect opportunity to do this.

[ricardoatsouza]

Now, I'm facing another issue. Somehow sonar-scanner cannot find scoverage.xml.
I keep seeing this in the logs:

ERROR: [scoverage] Report not found at /Users/username/Development/projectFolder/module-1/target/scala-2.12/scoverage-report
WARN: [scoverage] Report path not set for Module 1 module! [Module 1.sonar.scoverage.reportPath]

However, a ls module-1/target/scala-2.12/scoverage-report shows me that the file is there:

index.html     ingestion      ingestion.html overview.html  packages.html  scoverage.xml

I'm aware that this problem is not related to sbt-sonar, but since we are in this chat, do you have a better idea of why this might be happening?

[ricardoatsouza]

Actually, by setting manually the properties reportPath for both sub-projects solved the issue. Basically, what I did was adding these two lines to my build.sbt, in the sonarProperties variable:

  "module-1.sonar.scoverage.reportPath" -> "target/scala-2.12/scoverage-report/scoverage.xml",
  "module-2.sonar.scoverage.reportPath" -> "target/scala-2.12/scoverage-report/scoverage.xml",

Funny thing is: setting manually those variables should not actually be necessary, since this path was already being logged before. But this solution will solve it for now.

As a final check, I will update the Scala plugin in Sonarqube.

[mwz]

Thanks @ricardoatsouza for digging a little bit deeper.
I'd recommend sticking to SonarQube 5.6.7 for now until the sonar-scala plugin is compatible with 6.7.1 LTS. I've been doing some work in my fork of the project and I'm planning to make a release once it's ready, so you can keep an eye on sonar-scala/sonar-scala#5.
Your issues might be also related to how you set up your sbt project but it's difficult to say without seeing the config.
I think we can also improve sbt-sonar to automatically set sonar.sources, sonar.scoverage.reportPath and sonar.scala.scapegoat.reportPath for each module so you don't need to set this up manually (#9).

[ricardoatsouza]

@mwz Nice to hear that there are good stuff coming :)
Thanks for your support. I will have this repo in my watch list.
Cheers!