The waivers tab can be used to add, remove, edit and inspect the waivers.
Waivers are used to change the status of the hits that are matched by the waiver properties. Hits can also be removed using the same method. The status option can be set to:
DISABLED: hits are removed
ERROR: hits are reported as errors
WARNING: hits are reported as warnings
INFO: hits are reported as info
There are two types of waivers: Manually defined waivers can be created using
New... button from the Waivers tab. The
Waivers Editor dialog offers an easy way to configure a waiver. The parameters that can be configured are:
Waiver Name: an unique name for the waiver
Waiver File: the file where the waiver will be saved (from the waivers include tree)
Apply on: the scope of the waiver (it applies on matched or non matched hits)
Status: the status that will be applied to the matched hits
Check Names: the name of the checks this waiver applies to
Line Ranges: the line, or line ranges (StartLine:EndLine) this waiver must match
Message Patterns: the regular expression this waiver must match (Perl-like or simple regular expression)
The waiver will match a hit if all defined parameters match the hit properties (the check that generated the hit, line, file, or message). If a parameter is empty (not defined) it will match any value.
Code waivers can be inserted in code as comments with the following syntax: // @DVT_LINTER_WAIVER_START ["NAME"] STATUS [CHECK_1, CHECK_2]
code line
...
code line
// @DVT_LINTER_WAIVER_END
Where:
NAME: is the waiver name (optional) and must be enclosed within quotation marks
STATUS: is the status applied to the hits (mandatory) and must be one of the valid status values (DISABLE, ERROR, WARNING, INFO)
CHECK_1, CHECK_2: is a list of check names (optional) this waiver applies to, if it's not defined the waiver applies to all checks
|