Gradle plugin uses deprecated APIs

Hi,

I’m preparing the Micronaut Build plugins for the upcoming Gradle 9 release (expected end of this year/beginning of 2025) and as part of this, making sure to upgrade plugins we use internally. While most issues are fixed, we are seeing numerous deprecation warnings, a number of them coming from the Sonar plugin:

You can see a report of deprecated API usages here: Build Scan® | Develocity

May I ask your plans in removing use of deprecated APIs or behaviors, so that I plan accordingly?

Thanks!

1 Like

Hi,

Can you confirm that you’re using the latest version of the SonarScanner for Gradle?

 
Thx,
Ann

Sorry about this, realized I’m using 4.4.1.3373 : Build Scan® | Develocity, not the 5.x line!

1 Like

My previous post was marked as spam, but I can confirm I still get the same deprecations on latest plugin release. Unfortunately I can’t post links to scans anymore, so if you need them let me know how to share.

Hi,

Yeah, I have no idea why the spaminator suddenly went crazy on you, but I cleared all the flags. Sorry about that.

Can you not post links because they don’t exist anymore, or because of limits here in the Community?

 
Ann

Community says I can’t send links anymore

@melix @ganncamp It is in our backlog: [SCANGRADLE-135] - Jira

Due to the LTS, we needed to keep compatibility with earlier Gradle versions, and Gradle 9 wasn’t ready, so the change was postponed.

1 Like

Do you plan to release a version which doesn’t have deprecation warnings soon?

Hi,

Our next LTA is expected in January, releasing us from this backward-compatibility need. So I would look for the new scanner version after that.

 
HTH,
Ann

Thanks!