Continuation on "How to configure multi-module Gradle project..."

SonarQube Server / Community Build
, ,
1

Continuing the discussion from How to configure multi-module Gradle project to avoid "can’t be indexed twice" issue?:

When I removed sonar.sources my coverage dropped to 0%.
Looking at the code from SonarQube (“Code” tab) there is just a dash on the coverage numbers for my modules.

image
image1350×488 15.2 KB

Note: There were no new warnings from the scanner.

This was working before removing sonar.source.

Given that me following the recommendations (at least I think I was) obviously caused new issues, what are the exact recommendations for all the different sonar properties in a gradle project so that I may avoid this type of problems?

Some context:
SonarQube 9.9 LTS, SonarQube Gradle plugin 4.4.1.3373

Regards
Alix

1 Like
2

Hi Alix,

Can you share your analysis log, please?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide - redacted as necessary - will include that command as well.

This guide will help you find them.

 
Thx,
Ann

1 Like