=== on 4 Feb 2015, 10:43:14 Dinesh Bolkensteyn wrote:
Be careful, you cannot use ``++S1291++`` as a rule key to implement this rule.


You must use a key that contains "nosonar" (case-insenstive), because of this hack in SonarQube:

https://github.com/SonarSource/sonarqube/blob/master/sonar-plugin-api/src/main/java/org/sonar/api/issue/NoSonarFilter.java#L70


----
accepted = noSonarLines == null || !noSonarLines.contains(issue.line());
if (!accepted && StringUtils.containsIgnoreCase(issue.ruleKey().rule(), "nosonar")) {
  accepted = true;
}
----

=== on 8 Jan 2018, 17:57:09 Amaury Levé wrote:
Excludes C# and VB.Net as they don't use this mechanism.

=== on 3 Oct 2019, 20:08:11 Jonathan Hoopes wrote:
There is an issue with this rule where it is not able to be suppressed for imports.


 


How does this rule even make sense? This creates a warning for suppressing a warning, and there is no way to disable the warning of your suppression of the other warning in certain areas of your code.

=== on 3 Oct 2019, 20:58:34 Ann Campbell wrote:
\[~Pytry] if you'd like to start a discussion, please go to \https://community.sonarsource.com/