org.sonar.api.checks

Class NoSonarFilter

java.lang.Object

org.sonar.api.checks.NoSonarFilter

All Implemented Interfaces:

IssueFilter

Deprecated.

in 3.6. Replaced by NoSonarFilter

@Deprecated
public class NoSonarFilter
extends Object
implements IssueFilter

Since:

2.1

Constructor Summary

Constructors

Constructor and Description
NoSonarFilter(SonarIndex sonarIndex) Deprecated.

Method Summary

Methods

Modifier and Type	Method and Description
boolean	accept(Issue issue, IssueFilterChain chain) Deprecated. The accept method is called for each Issue created during analysis, to check if it has to be persisted.
void	addResource(Resource model, Set<Integer> noSonarLines) Deprecated.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

NoSonarFilter

public NoSonarFilter(SonarIndex sonarIndex)

Deprecated.

Method Detail

addResource

public void addResource(Resource model,
               Set<Integer> noSonarLines)

Deprecated.

accept

public boolean accept(Issue issue,
             IssueFilterChain chain)

Deprecated.

Description copied from interface: IssueFilter

The accept method is called for each Issue created during analysis, to check if it has to be persisted. Examples of use cases are:

• Ignoring or enforcing rules on specific resources
• Switching-off an issue based on its context (//NOSONAR comments, semantic annotations)

The chain parameter allows for fine control of the filtering logic: it is each filter's duty to either pass the issue to the next filter, by calling the IssueFilterChain.accept(org.sonar.api.issue.Issue) method, or return directly if the issue has to be accepted or not

Specified by:

accept in interface IssueFilter

Parameters:

issue - the issue being filtered

chain - the rest of the filters

Returns:

true to accept the issue, false to reject it, IssueFilterChain.accept(org.sonar.api.issue.Issue) to let the other filters decide.