No Issues reported for own developed sonar rules after Upgrade 9.9-> 25.2

SonarQube Server / Community Build Plugin Development
, ,
1

We have upgraded from SQ CE 9.9 → SQ CE 2025 (v25.2.0.102705) STANDARD EXPERIENCE.

We also upgraded from postgresql 12 → 13.

Everything went smooth and we can see our projects and the profiles we use. We also see our plugin and it’s rules.

We have our own java rules developed in our plugin so we made sure they were compatible with SQ 2025.

We updated pom.xml with the following changes:

<java.plugin.version>7.24.0.32100</java.plugin.version>  -->  <java.plugin.version>8.9.0.37768</java.plugin.version>

<sonar.version>9.14.0.375</sonar.version>  -->  <sonar.version>11.1.0.2693</sonar.version>

And we removed

<sonarQubeMinVersion>5.6</sonarQubeMinVersion>

When we run sonarqube with maven.

mvn sonar:sonar

We cannot see any errors however the rules that we have created are not applied. We know for sure that rules should detect issues. But there are zero issue.

We tried running maven with -X but no addtional clues.

We tried to create a new profile and add the the custom rules from our plugin but the result is the same.
We have tried to delete and republish projects but without any result.

Profile works if we import rules from SonarWay.

br,

//mikael

2

@ganncamp have you heard about this? Also do you know what we should look for in logs to make sure rules are applied?

4

Hey @eraonel

Please don’t tag people who aren’t involved in a thread. You may think it bumps it to the top of their list, but it does exactly the opposite!

There are a few changes between 9.9 and 25.2 that might be relevant, specifically around downloading only required 3rd party plugins. I’d suggest you read that announcement and see if any changes are required for your plugin.

I would also suggest you dig into your scanner logs a bit more. Do you see that the plugin has been downloaded (mvn sonar:sonar -X), and do you see the specific sensor for your plugin being executed?

5

A very easy way to see if you were affected by this change is to deactivate the optimization.

6

@Colin thx!
Yes the issue was that we had not added.

<requiredForLanguages>java</requiredForLanguages>

when packaging our custom plugin.
Now it is working.

1 Like
7

Great to hear! Thanks for following up.