Sourced from net.sourceforge.pmd:pmd-core's releases.

PMD 7.17.0 (12-September-2025)

12-September-2025 - 7.17.0

The PMD team is pleased to announce PMD 7.17.0.

This is a minor release.

Table Of Contents

• 🚀 New and noteworthy
  • ✨ New Rules
  • Deprecated Rules
  • CPD: New Markdown Report Format
• 🐛 Fixed Issues
• 🚨 API Changes
  • Deprecations
  • Experimental API
  • PMD Report Format CSV
  • Rule Test Schema
  • Deprecations
• ✨ Merged pull requests
• 📦 Dependency updates
• 📈 Stats

🚀 New and noteworthy

✨ New Rules

This release brings several new rules for both Java and Apex. Please try them out and submit feedback on our issue tracker!

• The new apex rule AnnotationsNamingConventions enforces that annotations are used consistently in PascalCase.
  The rule is referenced in the quickstart.xml ruleset for Apex.
• The new java rule TypeParameterNamingConventions replaces the now deprecated rule GenericsNaming. The new rule is configurable and checks for naming conventions of type parameters in generic types and methods. It can be configured via a regular expression.
  By default, this rule uses the standard Java naming convention (single uppercase letter).
  The rule is referenced in the quickstart.xml ruleset for Java.
• The new java rule OverrideBothEqualsAndHashCodeOnComparable finds missing hashCode() and/or equals() methods on types that implement Comparable. This is important if instances of these classes are used in collections. Failing to do so can lead to unexpected behavior in sets which then do not conform to the Set interface. While the Set interface relies on equals() to determine object equality, sorted sets like TreeSet use compareTo() instead. The same issue can arise when such objects are used as keys in sorted maps.
  This rule is very similar to OverrideBothEqualsAndHashcode which has always been

... (truncated)

• d2942d5 [release] prepare release pmd_releases/7.17.0
• 76cc98a Prepare pmd release 7.17.0
• 58dfb17 [doc] Update release notes - add missing new rule fix issues
• 1b23cb3 [java] More detailed message for AvoidInstanceofChecksInCatchClause (#6009)
• f8a962a Merge branch 'main' into instanceof-message
• ce3b01f [core] Fix #5849: Support Markdown Output for CPD Reports (#6008)
• 2e84a82 Merge branch 'main' into pr-6009
• d55bea2 [doc] Update release notes (#6009)
• 59ff641 Merge branch 'main' into pr-6008
• d34dbfc [doc] Update release notes (#6008, #5849)
• Additional commits viewable in compare view

Sourced from net.sourceforge.pmd:pmd-java's releases.

PMD 7.17.0 (12-September-2025)

12-September-2025 - 7.17.0

The PMD team is pleased to announce PMD 7.17.0.

This is a minor release.

Table Of Contents

• 🚀 New and noteworthy
  • ✨ New Rules
  • Deprecated Rules
  • CPD: New Markdown Report Format
• 🐛 Fixed Issues
• 🚨 API Changes
  • Deprecations
  • Experimental API
  • PMD Report Format CSV
  • Rule Test Schema
  • Deprecations
• ✨ Merged pull requests
• 📦 Dependency updates
• 📈 Stats

🚀 New and noteworthy

✨ New Rules

This release brings several new rules for both Java and Apex. Please try them out and submit feedback on our issue tracker!

• The new apex rule AnnotationsNamingConventions enforces that annotations are used consistently in PascalCase.
  The rule is referenced in the quickstart.xml ruleset for Apex.
• The new java rule TypeParameterNamingConventions replaces the now deprecated rule GenericsNaming. The new rule is configurable and checks for naming conventions of type parameters in generic types and methods. It can be configured via a regular expression.
  By default, this rule uses the standard Java naming convention (single uppercase letter).
  The rule is referenced in the quickstart.xml ruleset for Java.
• The new java rule OverrideBothEqualsAndHashCodeOnComparable finds missing hashCode() and/or equals() methods on types that implement Comparable. This is important if instances of these classes are used in collections. Failing to do so can lead to unexpected behavior in sets which then do not conform to the Set interface. While the Set interface relies on equals() to determine object equality, sorted sets like TreeSet use compareTo() instead. The same issue can arise when such objects are used as keys in sorted maps.
  This rule is very similar to OverrideBothEqualsAndHashcode which has always been

... (truncated)

• d2942d5 [release] prepare release pmd_releases/7.17.0
• 76cc98a Prepare pmd release 7.17.0
• 58dfb17 [doc] Update release notes - add missing new rule fix issues
• 1b23cb3 [java] More detailed message for AvoidInstanceofChecksInCatchClause (#6009)
• f8a962a Merge branch 'main' into instanceof-message
• ce3b01f [core] Fix #5849: Support Markdown Output for CPD Reports (#6008)
• 2e84a82 Merge branch 'main' into pr-6009
• d55bea2 [doc] Update release notes (#6009)
• 59ff641 Merge branch 'main' into pr-6008
• d34dbfc [doc] Update release notes (#6008, #5849)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)