Sonarqube is not pointing out custom rules issues in the analysis

I am developing a custom rule in Java, but during the SonarQube analysis, the issue is not being flagged, even though it is correctly detected by SonarLint.

I have provided a detailed explanation of the issue here: ISSUES.md

All the source code can be found in the repository: sonar-custom-rules-java-plugin

No replies yet; could it be in the incorrect category?

Nope – it’s just a niche topic that not too many people are equipped to answer. So it takes some time. Feel free to contribute back to this community and free up somebody’s time!

I created a topic, when can I expect a response?

This is an open community with people volunteering their free time to provide assistance. We’re eager to contribute to the community, but you are not guaranteed a fast response.

Be patient

  • Wait a few days before bumping a topic that hasn’t received a response.
  • Do not @name mention individuals not involved in the topic.

Contribute as much as you expect to receive

  • Contribute to the community (helping others) as much as you expect to receive help.
1 Like

You need to check at first all setttings of your analyis, i.e.

  • use loglevel DEBUG to see all details for the analysis
  • is the file included for the scan ?
  • is your custom rule really part of the quality profile ?
  • … etc.

I don’t want to analyze your implementation in detail, but I have created a bunch of
custom rules over the years and can give you the following advice:

If you want to improve your implementation, use the mentioned

as inspiration.

When creating custom rules this is always a good source of information

1 Like

Sorry, I thought I was in the wrong category.