Both the Warnings Plug-in, and Violations Lib used by Violation Comments to Bitbucket Server Plugin, are able to parse JCReport files, but they disagree on how the severity levels should be formatted.

• Warnings Plug-in wants capitalized strings "Error" and "Warning": https://github.com/jenkinsci/warnings-plugin/blob/warnings-4.64/src/main/java/hudson/plugins/warnings/parser/jcreport/JcReportParser.java#L83

• Violations Lib wants lower-case strings "error" and "warning": https://github.com/tomasbjerre/violations-lib/blob/1.37/src/main/java/se/bjurr/violations/lib/parsers/JCReportParser.java#L67

I was writing a script to convert a DocFX log from JSON to something that both plugins would be able to parse, and I chose the JCReport format because it is simple enough, supports newlines within messages, supports multiple severity levels, and does not require programming-specific information like class names. This mismatch however means that the script now needs to generate a separate JCReport file for each plugin. I don't know whether JCReport itself would capitalize the severity levels.

I'm filing this under the warnings-plugin and violation-comments-to-github-plugin components because there is no violation-comments-to-stash-plugin component and both of those violation-comments-* plugins use violations-lib.