Ullrich Hafner

Another location: - https://github.com/uhafner/echarts-build-trends/commit/7496ccb81b0274596270fdeefe6023648d3f6c26 - https://github.com/uhafner/echarts-build-trends/blob/7496ccb81b0274596270fdeefe6023648d3f6c26/src/main/java/edu/hm/hafner/echarts/TreeNode.java#L99

I also detected several new violations in my codebase that are caused by the changed behavior of this rule in the 7.x release (see https://github.com/uhafner/codingstyle/pull/978/files). I was able to suppress...

Here is another example: - PR: https://github.com/jenkinsci/warnings-ng-plugin/pull/1782 - Compile log: https://github.com/jenkinsci/warnings-ng-plugin/pull/1782/checks?check_run_id=27089938679 - Parsed Class: https://github.com/jenkinsci/warnings-ng-plugin/blob/2fcf545b501fe5cfbbb052db5ab22360a7046907/plugin/src/main/java/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner.java

Thanks for making the mapping configurable! The PMD parser (and the associated plugin) has been integrated into the warnings plugin (see [PMD tool descriptor](https://github.com/jenkinsci/warnings-plugin/blob/5.0/src/main/java/io/jenkins/plugins/analysis/warnings/Pmd.java)). These changes are not yet released...

The analysis core plugin is end-of-life. All feature changes should be part of the new [Warnings Next Generation Plugin](https://github.com/jenkinsci/warnings-ng-plugin). Are you still using the analysis-core plugin?

Seems that assert-core reports messages that could be read by IntelliJ. Just the custom assertions do use a different format (and exception type). Would be nice if the assert-core code...

Don't we use badges in other areas for the same thing? When should I use a badge and when this new style? It makes sense to clarify in the design...

It took me a while to understand that the result is visible in freestyle jobs only. Isn't the PR that unifies the console in pipelines and freestyle jobs already merged?...

@dependabot rebase

@dependabot rebase