Edit me

24-April-2021 - 6.34.0

The PMD team is pleased to announce PMD 6.34.0.

This is a minor release.

New and noteworthy

New rules

Modified rules

  • The Apex rule ApexCRUDViolation does not ignore getters anymore and also flags SOQL/SOSL/DML operations without access permission checks in getters. This will produce false positives now for VF getter methods, but we can’t reliably detect, whether a getter is a VF getter or not. In such cases, the violation should be suppressed.

Deprecated rules

Fixed Issues

  • apex-performance
    • #3198: [apex] OperationWithLimitsInLoopRule: Support more limit consuming static method invocations
  • apex-security
    • #3202: [apex] ApexCRUDViolationRule fails to report CRUD violation on COUNT() queries
    • #3210: [apex] ApexCRUDViolationRule false-negative on non-VF getter
  • java-bestpractices
    • #3190: [java] Use StandardCharsets instead of Charset.forName
    • #3224: [java] UnusedAssignment crashes with nested records
  • java-codestyle
    • #3128: [java] New rule UnnecessaryImport, deprecate DuplicateImports, ImportFromSamePackage, UnusedImports
  • java-errorprone
    • #2757: [java] CloseResource: support Lombok’s @Cleanup annotation
    • #3169: [java] CheckSkipResult: NPE when using pattern bindings

API Changes

No changes.

External Contributions

  • #3193: [java] New rule: UseStandardCharsets - Andrea Aime
  • #3198: [apex] OperationWithLimitsInLoopRule: Support more limit consuming static method invocations - Jonathan Wiesel
  • #3211: [apex] ApexCRUDViolationRule: Do not assume method is VF getter to avoid CRUD checks - Jonathan Wiesel
  • #3234: [apex] ApexCRUDViolation: COUNT is indeed CRUD checkable since it exposes data (false-negative) - Jonathan Wiesel


  • 74 commits
  • 18 closed tickets & PRs
  • Days since last release: 27