Fix NoPluginFoundForPrefixException for sonar - #2020
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
|
poojah-adyen
enabled auto-merge
July 27, 2026 10:25
andrej-gajduk-adyen
approved these changes
Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
CI's SonarCloud step started failing with No plugin found for prefix 'sonar'.
This replaces
sonar:sonarwith the supported, fully-qualified goalorg.sonarsource.scanner.maven:sonar-maven-plugin:sonarin both workflows (javaci.yml, sonarcloud.yml). The version is ,intentionally omitted so Maven resolves the latest scanner release automatically — no manual version bumps required.Tested scenarios
Fixed issue: