Not sure if error or missing feature. But the thing is that we have a common project that contains rule files for all quality plugins and one of them is PMD. The projects are set up in a way that they always fetch the latest bundle of rulefiles (so we can update the quality gates without changing the projects). So far so good,
But the issue is that we updated PMD in some project and noticed that of the rules does not suite our needs. So we suppresed it... And now the issue. Not all projects have the latest PMD -> Unable to exclude rules [AvoidUncheckedExceptionsInSignatures]; perhaps the rule name is mispelled?
Is it somehow possible to get rid of this behavior and set PMD to tolerant mode. Maybe write some warning to log... but not fail the build? From my perspective its much cleaner approach, as not applying exclusion at all (the worst case) cannot lower the quality of the checked product...
Essentially this makes any changes to shared rulesets to be backward incompatible...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4