Frontend coverage drop caused by update 2025.5 and sonar maven plugin

SonarQube Server / Community Build
1

We use Sonar with a multi modul project with java and angular/typescript.
After the update of the Server to 2025.5 the LoC and Coverage dropped because the angular/typescript was not analysed anymore.

We use the maven sonar plugin with the current version 5.2.0.4988.
As documented we used in our frontend module in the pom.xml the property for the reportPath and it worked the whole time:
<sonar.javascript.lcov.reportPaths>
myPath/lcov.info
</sonar.javascript.lcov.reportPaths>

After the update this did not work anymore.

The only workaround is to use the command line parameters with -D like
mvn sonar:sonar -Dsonar.javascript.lcov.reportPaths=myProjectPath/lcov.info

I could confirm these behavior with the sonar.verbose=true and and the sonar.log.level=debug that the pom.xml property result in a sonar.javascript.lcov.reportPaths= empty log and the -D property got the right path.

Others properties might be affected too.

2

we are having the exact same issue. setting the property via the gradle plugin like so:

sonarqube {
  properties {
    // ...
    property 'sonar.javascript.lcov.reportPaths', project.sonarCoveragePaths
    // ...
  }
}

did result in 0% coverage checks for the frontend.

only after finding this thread, and setting the property via the Web UI (http://my-sonar-example.com/project/settings?id=design-system&category=JavaScript+%2F+TypeScript > LCOV Files), the coverage started working again.

we are using sonar developer, self hosted via the official helm chart (sonarqube 2025.5.0 · sonarsource/sonarqube) and id "org.sonarqube" version "6.3.1.5724" as gradle plugin.

is this a problem with the gradle plugin, or sonar itself?
we recently upgraded from 24.12(December Release) to the latest 2025.5.0 version; in version 24.12 it worked fine.

3

also, maybe related? New architecture step in sonar analysis : skipping load fail and raised error : null - #7 by Colin

4

Hi all,

Welcome to the community and thanks for this report!

@Andreas_Makovskij you say both coverage and LOC dropped. That means your JS is no longer being analyzed at all?

How were both of you previously including your JS in analysis? By passing an explicit sonar.sources value or by using sonar.maven.scanAll? And you say this changed with the upgrade. Before the upgrade were you using this same version of the scanner? Or did you upgrade server and scanner together?

 
Thx,
Ann

5

we are using sonar.sources.

we upgraded sonar via the helm chart (chart version); we did not make any other updates to other components

1 Like
7

Hi,

Thanks for the details.

In fact, this turns out to be a (somewhat) known issue identified on SonarQube Cloud in late September. We’re working on the fix, but it’s not clear to me whether we’ll issue a patch for this.

I’ve flagged this for the PMs. In the meantime, fortunately you’ve found a workaround.

 
Ann