Custom plugin for Natural language is not working after the Sonar community upgrade

SonarQube Server / Community Build Plugin Development
1

Hi,

We are upgrading our sonarqube community edition server from v9.9 LTA to 25.8.0.112029. We are using zip installation. We have followed the below path for the upgrade

v9.9 LTA → 24.12.0.100206 And then
24.12.0.100206 → 25.8.0.112029
Sonar server upgrade is successful. Along with the Sonarqube server upgrade we are upgrading the custom plugin created by us for Natural Language. This plugin was working perfectly with the sonarqube server v9.9 LTA but after the upgrade this plugin is not able to index the Natural language code as Natural language.
We are seeing in the logs “Natural Source code is indexed with no language“.

To upgrade the custom Natural plugin we have upgraded the following dependencies in plugin source code and plugin is being deployed successfully in Sonarqube Server.
sonar-plugin-api from 9.14.0.375 to 13.0.0.3026
sonar-plugin-api-impl from 8.6.0.39681 to 25.8.0.112029
Due to this upgrade, we found few of the methods have been deprecated in the Profile class so we have updated those classes too. For example,
RuleFinder
RulesProfile

Before the upgrade we were getting below message in the logs for Natural Source code during the sonar analysis of Natural source code
DEBUG: ‘Lib/SRC/XAFXCPX0.NSA’ indexed with language ‘nsp’

After the sonar server and plugin upgrade, we are getting the below message in the logs for Natural Source code during the sonar analysis of Natural source code
DEBUG ‘Lib/SRC/XMQMD2V.NSL’ indexed with no language

Could anyone please suggest what could be the problem that Natural language code is not being indexed properly ?

Thanks & Regards,
Gourav Arora

2

Hey there.

Have a look over here:

3

Hi Colin,

The plugin deploys successfully, but Natural files are still not indexed as a language.
Before upgrade:**
DEBUG: ‘Lib/SRC/XAFXCPX0.NSA’ indexed with language ‘natural’

After upgrade:**
DEBUG: ‘Lib/SRC/XMQMD2V.NSL’ indexed with no language

Yes, I have gone through the post →(   )regarding Plugin-RequiredForLanguages.I tried adding it in my pom as below:

<plugin>
<groupId>org.sonarsource.sonar-packaging-maven-plugin</groupId>
<artifactId>sonar-packaging-maven-plugin</artifactId>
<version>1.23.0.740</version>
<extensions>true</extensions>
<configuration>
<pluginClass>at.spardat.sonar.plugins.natural.NaturalPlugin</pluginClass>
<requiredForLanguages>natural</requiredForLanguages>
</configuration>
</plugin>

My Natural language class uses the following:
java
public static final String KEY = “natural”;

super(KEY, “Natural”);
But even after adding

natural

the plugin still does not register, and Natural source code continues to show as indexed with no language
Questions:

  1. Am I missing something in linking the language key to the plugin manifest?
  2. Should the KEY in my Natural class match exactly with in the pom?
  3. Is there any additional change needed in sonar-packaging-maven-plugin config for plugins on SonarQube 25.8?
    Any guidance would be really helpful, I’m stuck at getting Sonar to recognize my language after the upgrade.

Thanks in advance.

4

If the plugin is open source, please consider sharing it here so we can review it more thoroughly.

Additionally, you may want to try disabling analyzer download optimization. If disabling this option resolves the issue, it indicates that the problem is likely linked to the changes you recently made, as mentioned in my previous post.