PMD Release Notes

26-February-2022 - 6.43.0

The PMD team is pleased to announce PMD 6.43.0.

This is a minor release.

New and noteworthy

Fixed Issues

• core
  • #3427: [core] Stop printing CLI usage text when exiting due to invalid parameters
  • #3768: [core] SARIF formatter reports multiple locations when it should report multiple results
• doc
  • #2502: [doc] Add floating table-of-contents (toc) on the right
  • #3807: [doc] Document Ant Task parameter threads
• java
  • #3698: [java] Parsing error with try-with-resources and qualified resource
• java-bestpractices
  • #3605: [java] SwitchStmtsShouldHaveDefault triggered when default case is present
• java-codestyle
  • #278: [java] ConfusingTernary should treat != null as positive condition
• java-performance
  • #3374: [java] UseStringBufferForStringAppends: Wrong example in documentation
• misc
  • #3759: [lang-test] Upgrade dokka maven plugin to 1.4.32
• plsql
  • #3746: [plsql] Parsing exception “Less than or equal to/Greater than or equal to” operators in DML statements

API Changes

Deprecated API

Some API deprecations were performed in core PMD classes, to improve compatibility with PMD 7.

• Report: the constructor and other construction methods like addViolation or createReport
• RuleContext: all constructors, getters and setters. A new set of stable methods, matching those in PMD 7, was added to replace the addViolation overloads of AbstractRule. In PMD 7, RuleContext will be the API to report violations, and it can already be used as such in PMD 6.
• The field configuration is unused and will be removed.

Internal API

Those APIs are not intended to be used by clients, and will be hidden or removed with PMD 7.0.0. You can identify them with the @InternalApi annotation. You’ll also get a deprecation warning.

• RuleSet: methods that serve to apply rules, including apply, start, end, removeDysfunctionalRules
• AbstractAccumulatingRenderer#renderFileReport is internal API and should not be overridden in own renderers.

Changed API

It is now forbidden to report a violation:

• With a null node
• With a null message
• With a null set of format arguments (prefer a zero-length array)

Note that the message is set from the XML rule declaration, so this is only relevant if you instantiate rules manually.

RuleContext now requires setting the current rule before calling apply. This is done automatically by RuleSet#apply and such. Creating and configuring a RuleContext manually is strongly advised against, as the lifecycle of RuleContext will change drastically in PMD 7.

External Contributions

• #3767: [core] Update GUI.java - Vyom Yadav
• #3804: [doc] Add floating table of contents (issue #2502) - JerritEic

Stats

• 49 commits
• 22 closed tickets & PRs
• Days since last release: 27