@cecertemel I went through the steps I described above to add a single rule to a fork of the Wintellect analyzer, generate a plugin and add it to SonarQube. The new custom rule appeared as expected:
I then added two more rules, rebuilt the assembly, updated the cached zip file, regenerated the plugin and added it to SonarQube. All three custom rules are visible in SonarQube:
The fork I created is here, and this is the jar with three rules (renamed to a zip): wintellectanalyzers-plugin-1.0.6.jar.zip (479.7 KB)
I was using SonarQube Community edition v8.6.1.
It looks like the plugin generator and SonarQube are working as expected, which suggests the problem is somewhere in the process you are following.
Starting at the beginning:
- independently of SonarQube, what happens if you try to use your modified analyzer NuGet package in VS project - do your custom rules appear?
- Next, does the console output from the
RoslynSonarQubePluginGenerator contain the expected number of analysis rules?