SonarScanner for Gradle 7.0: Support of Gradle 9

EDIT (2025-10-24): The post was edited to point to the latest release of the scanner 7.0.1 which is functionally identical to 7.0.0 but updates the signature files made available on the Gradle plugin portal.

TL;DR: Release 7.0.1 brings basic support for Gradle 9. Please beware that this release targets users who encountered issues in project configuration after migrating to Gradle 9. Users of version 6.3.1 who did not experience any issues are encouraged to upgrade with caution.

We are pleased to announce the release of the SonarScanner for Gradle 7.0 now with basic support of Gradle 9. This new release improves scanner behavior by reducing cross-project configuration to a minimum. This change is designed to prevent crashes at configuration time previously reported by users who had migrated their codebase to Gradle 9.

While this technical change should not affect the quality or configuration of your analysis, your first analysis after migration might take slightly longer than previously due to the updated scanner configuration.

We encourage users whose analysis has been disrupted since migrating to Gradle 9 to try the SonarScanner Gradle version 7.0 and share their experience with us. Feedback from users who have not encountered any issue with previous versions of the scanner is also welcome. However, we advise these users to upgrade with caution, as some complex project configurations might lead to degraded analysis results in the form of a major drop in legitimate issues.

Should you encounter any issues with this new release, please open a new thread for discussion.

6 Likes

What exactly means “upgrade with caution"? Is there any breaking change?

1 Like

Hi @pedrovasconcellos,

What exactly means “upgrade with caution"? Is there any breaking change?

We have changed the way we gather classpath information with this release in order to fix issues encountered by some users. During development, we observed that some projects would completely lose classpath information leading to a loss of legitimate issues.

When upgrading, consider looking for:

  1. Any breakage in analysis
  2. A loss of legitimate existing issues
  3. New error or warning messages in the analysis logs

If any of these manifest themselves in your analysis, please open a new thread so we can investigate the issues.

Cheers,

Dorian