The unique id of the analysis.
The relevance of the issue.
The issue in one short sentence (no line breaks)!
A string that uses small letters and which describes the category of the issue. The category basically describes the property of the software that is affected by this issue (see IssueCategory for further details).
A string that uses small letters and which describes the kind of the issue. The kind describes how this issue manifests itself in the source code (see IssueKind for further details).
The source code locations related to this issue. This seq must not be empty!
The unique id of the analysis.
A string that uses small letters and which describes the category of the issue.
A string that uses small letters and which describes the category of the issue. The category basically describes the property of the software that is affected by this issue (see IssueCategory for further details).
A string that uses small letters and which describes the kind of the issue.
A string that uses small letters and which describes the kind of the issue. The kind describes how this issue manifests itself in the source code (see IssueKind for further details).
The source code locations related to this issue.
The source code locations related to this issue. This seq must not be empty!
The relevance of the issue.
The issue in one short sentence (no line breaks)!
Representation of this issue well suited for console output if the console supports ANSI color escapes.
Representation of this issue well suited for console output if the console supports ANSI color escapes.
If you are generating output related to (a line in) a class file, use a format as used by other compilers, e.g., CLANG and GCC:
FILENAME:[LINE:[COLUMN:]] TYPE: MESSAGEwhere FILENAME denotes the name of the file, LINE is the line number if available, COLUMN is the column – which is usually not available when you analyze class files and TYPE identifies the type of the message (e.g., "note", "warning", "error", "fatal error").
Line and column information is optional.
If the real filename is not available use the fully qualified name of the class in binary notation (i.e., using "/" to separate the package qualifiers) with the suffice ".class" appended.
Note that the space after the location information is required.
demo/Buggy.class:100: warning: protected field in final class
A basic representation of this issue well suited for console output.
A basic representation of this issue well suited for console output.
A representation of this issue well suited for output to the Eclipse IDE console.
A representation of this issue well suited for output to the Eclipse IDE console.
A representation of this issue using the Issues Description Language (which is a JSON dialect.)
A representation of this issue using the Issues Description Language (which is a JSON dialect.)
An (x)HTML5 representation of the issue, well suited for browser output.
An (x)HTML5 representation of the issue, well suited for browser output.
Describes some issue found in source code.
The unique id of the analysis.
The relevance of the issue.
The issue in one short sentence (no line breaks)!
A string that uses small letters and which describes the category of the issue. The category basically describes the property of the software that is affected by this issue (see IssueCategory for further details).
A string that uses small letters and which describes the kind of the issue. The kind describes how this issue manifests itself in the source code (see IssueKind for further details).
The source code locations related to this issue. This seq must not be empty!