PMD Release Notes

22-March-2024 - 7.0.0

🎉 After a long time, we’re excited to bring you now the next major version of PMD! 🎉

Since this is a big release, we provide here only a concise version of the release notes. We prepared a separate page with the full Detailed Release Notes for PMD 7.0.0.

🤝🙏 Many thanks to all users and contributors who were testing the release candidates and provided feedback and/or PRs!

✨ PMD 7…

• …has a new logo
• …analyzes Java 21 and Java 22 projects with even better type resolution and symbol table support
• …analyzes Kotlin and Swift
• …analyzes Apex with a new parser
• …finds duplicated code in Coco, Julia, TypeScript
• …ships 11 new rules and tons of improvements for existing rules
• …provides a new CLI interface with progress bar
• …supports Antlr based languages
• …and many more enhancements

💥 Note: Since PMD 7 is a major release, it is not a drop-in replacement for PMD 6.55.0. A detailed documentation of required changes are available in the Migration Guide for PMD 7.

Changes since 7.0.0-rc4

This section lists the most important changes from the last release candidate. The remaining section describes the complete release notes for 7.0.0.

New and Noteworthy

Maven PMD Plugin compatibility with PMD 7

In order to use PMD 7 with maven-pmd-plugin a new compatibility module has been created. This allows to use PMD 7 by simply adding one additional dependency:

1. Follow the guide Upgrading PMD at Runtime
2. Add additionally the following dependency:

<dependency>
  <groupId>net.sourceforge.pmd</groupId>
  <artifactId>pmd-compat6</artifactId>
  <version>${pmdVersion}</version>
</dependency>

It is important to add this dependency as the first in the list, so that maven-pmd-plugin sees the (old) compatible versions of some classes.

This module is available beginning with version 7.0.0-rc4 and will be there at least for the first final version PMD 7 (7.0.0). It’s not decided yet, whether we will keep updating it, after PMD 7 is finally released.

Note: This compatibility module only works for the built-in rules, that are still available in PMD 7. E.g. you need to review your rulesets and look out for deprecated rules and such. See the use case I’m using only built-in rules in the Migration Guide for PMD 7.

As PMD 7 revamped the Java module, if you have custom rules, you need to migrate these rules. See the use case I’m using custom rules in the Migration Guide.

Note: Once the default version of PMD is upgraded to PMD7 in maven-pmd-plugin (see MPMD-379), this compatibility module is no longer needed. The module pmd-compat6 might not be maintained then any further, hence it is already declared as deprecated.

No guarantee is given, that the (deprecated) module pmd-compat6 is being maintained over the whole lifetime of PMD 7.

Java 22 Support

This release of PMD brings support for Java 22. There are the following new standard language features, that are supported now:

• JEP 456: Unnamed Variables & Patterns

PMD also supports the following preview language features:

• JEP 447: Statements before super(…) (Preview)
• JEP 459: String Templates (Second Preview)
• JEP 463: Implicitly Declared Classes and Instance Main Methods (Second Preview)

In order to analyze a project with PMD that uses these language features, you’ll need to enable it via the environment variable PMD_JAVA_OPTS and select the new language version 22-preview:

export PMD_JAVA_OPTS=--enable-preview
pmd check --use-version java-22-preview ...

Note: Support for Java 20 preview language features have been removed. The version “20-preview” is no longer available.

Swift Support

• limited support for Swift 5.9 (Macro Expansions)

Groovy Support (CPD)

• We now support parsing all Groovy features from Groovy 3 and 4.
• We now support suppression through CPD-ON/CPD-OFF comment pairs.
• See PR #4726 for details.

Updated PMD Designer

This PMD release ships a new version of the pmd-designer. The designer artifact has been renamed from “pmd-ui” to “pmd-designer”. While the designer still works with Java 8, the recommended Java Runtime is Java 11 (or later) with OpenJFX 17 (or later).

For the detailed changes, see PMD Designer Changelog (7.0.0).

Apex Support: Replaced Jorje with fully open source front-end

When PMD added Apex support with version 5.5.0, it utilized the Apex Jorje library to parse Apex source and generate an AST. This library is however a binary-blob provided as part of the Salesforce Extensions for VS Code, and it is closed-source.

This causes problems, if binary blobs are not allowed by e.g. a company-wide policy. In that case, the Jorje library prevented that PMD Apex could be used at all.

Also having access to the source code, enhancements and modifications are easier to do.

Under the hood, we use two open source libraries instead:

• apex-parser originally by Kevin Jones (@nawforce). This project provides the grammar for a ANTLR based parser.
• Summit-AST by Google (@google) This project translates the ANTLR parse tree into an AST, that is similar to the AST Jorje provided. Note: This is not an official Google product.

Although the parser is completely switched, there are only little known changes to the AST. These are documented in the Migration Guide for PMD 7: Apex AST.

With the new Apex parser, the new language constructs like User Mode Database Operations and the new Null Coalescing Operator ?? can be parsed now. PMD should be able to parse Apex code up to version 60.0 (Spring ‘24).

See #3766 for details.

Contributors: Aaron Hurst (@aaronhurst-google), Edward Klimoshenko (@eklimo)

Changed: Visualforce

There was an inconsistency between the naming of the maven module and the language id. The language id used the abbreviation “vf”, while the maven module used the longer name “visualforce”. This has been solved by renaming the language module to its full name “visualforce”. The java packages have been renamed as well.

If you import rules, you also need to adjust the paths, e.g.

• category/vf/security.xml ➡️ category/visualforce/security.xml

Changed: HTML support

Support for HTML was introduced in PMD 6.55.0 as an experimental feature. With PMD 7.0.0 this is now considered stable.

Changed: Kotlin support

Support for Kotlin was introduced with PMD 7.0.0-rc1 as an experimental feature. With PMD 7.0.0 this is now considered stable.

Changed: Velocity Template Language (VTL)

The module was named just “vm” which was not a good name. Its module name, language id and package names have been renamed to “velocity”.

If you import rules, you also need to adjust the paths, e.g.

• category/vm/... ➡️ category/velocity/...

Rule Changes

New Rules

• OperationWithHighCostInLoop finds Schema class methods called in a loop, which is a potential performance issue.
• UseExplicitTypes reports usages of var keyword, which was introduced with Java 10.
• MissingEncoding finds XML files without explicit encoding.

Changed Rules

• EmptyControlStatement: The rule has a new property to allow empty blocks when they contain a comment (allowCommentedBlocks).
• MethodNamingConventions: The deprecated rule property skipTestMethodUnderscores has been removed. It was actually deprecated since PMD 6.15.0, but was not mentioned in the release notes back then. Use the property testPattern instead to configure valid names for test methods.
• CommentRequired: The deprecated property headerCommentRequirement has been removed. Use the property classCommentRequirement instead.
• NonSerializableClass: The deprecated property prefix has been removed without replacement. In a serializable class all fields have to be serializable regardless of the name.

Renamed Rulesets

• category/vf/security.xml ➡️ category/visualforce/security.xml
• category/vm/bestpractices.xml ➡️ category/velocity/bestpractices.xml
• category/vm/design.xml ➡️ category/velocity/design.xml
• category/vm/errorprone.xml ➡️ category/velocity/errorprone.xml

Removed Rules

The following previously deprecated rules have been finally removed:

• Apex
  • performance.xml/AvoidSoqlInLoops (deleted) ➡️ use OperationWithLimitsInLoop
  • performance.xml/AvoidSoslInLoops (deleted) ➡️ use OperationWithLimitsInLoop
  • performance.xml/AvoidDmlStatementsInLoops (deleted) ➡️ use OperationWithLimitsInLoop
• Java
  • design.xml/ExcessiveClassLength (deleted) ➡️ use NcssCount
  • design.xml/ExcessiveMethodLength (deleted) ➡️ use NcssCount
  • errorprone.xml/BeanMembersShouldSerialize (deleted) ➡️ use NonSerializableClass
  • errorprone.xml/EmptyFinallyBlock (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyIfStmt (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyInitializer (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyStatementBlock (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyStatementNotInLoop (deleted) ➡️ use UnnecessarySemicolon
  • errorprone.xml/EmptySwitchStatements (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptySynchronizedBlock (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyTryBlock (deleted) ➡️ use EmptyControlStatement
  • errorprone.xml/EmptyWhileStmt (deleted) ➡️ use EmptyControlStatement

Removed deprecated rulesets

The following previously deprecated rulesets have been removed. These were the left-over rulesets from PMD 5. The rules have been moved into categories with PMD 6.

Fixed issues

• cli
  • #4594: [cli] Change completion generation to runtime
  • #4685: [cli] Clarify CPD documentation, fix positional parameter handling
  • #4723: [cli] Launch fails for “bash pmd”
• core
  • #1027: [core] Apply the new PropertyDescriptor<Pattern> type where applicable
  • #3903: [core] Consolidate n.s.pmd.reporting package
  • #3905: [core] Stabilize tree export API
  • #3917: [core] Consolidate n.s.pmd.lang.rule package
  • #4065: [core] Rename TokenMgrError to LexException, Tokenizer to CpdLexer
  • #4309: [core] Cleanups in XPath area
  • #4312: [core] Remove unnecessary property color and system property pmd.color in TextColorRenderer
  • #4313: [core] Remove support for <lang>-<ruleset> hyphen notation for ruleset references
  • #4314: [core] Remove ruleset compatibility filter (RuleSetFactoryCompatibility) and CLI option --no-ruleset-compatibility
  • #4348: [core] Consolidate @InternalApi classes
  • #4349: [core] Cleanup remaining experimental and deprecated API
  • #4378: [core] Ruleset loading processes commented rules
  • #4674: [core] WARNING: Illegal reflective access by org.codehaus.groovy.reflection.CachedClass
  • #4694: [core] Fix line/col numbers in TokenMgrError
  • #4717: [core] XSLTRenderer doesn’t close report file
  • #4750: [core] Fix flaky SummaryHTMLRenderer
  • #4782: [core] Avoid using getImage/@Image
• doc
  • #995: [doc] Document API evolution principles as ADR
  • #2511: [doc] Review guides for writing java/xpath rules for correctness with PMD 7
  • #3175: [doc] Document language module features
  • #4308: [doc] Document XPath API @DeprecatedAttribute
  • #4319: [doc] Document TypeRes API and Symbols API
  • #4659: [doc] Improve ant documentation
  • #4669: [doc] Add bld PMD Extension to Tools / Integrations
  • #4676: [doc] Clarify how CPD --ignore-literals and --ignore-identifiers work
  • #4704: [doc] Multivalued properties do not accept | as a separator
• miscellaneous
  • #4699: Make PMD buildable with java 21
  • #4586: Use explicit encoding in ruleset xml files
  • #4642: Update regression tests with Java 21 language features
  • #4736: [ci] Improve build procedure
  • #4741: Add pmd-compat6 module for maven-pmd-plugin
  • #4749: Fixes NoSuchMethodError on processing errors in pmd-compat6
  • #4776: [ci] Upgrade to ruby 3
  • #4796: Remove deprecated and release rulesets
  • #4823: Update to use renamed pmd-designer
  • #4827: [compat6] Support config errors and cpd for csharp
  • #4830: Consolidate packages in each maven module
  • #4867: [dist] ./mvnw command not found in dist-src
• apex
  • #3766: [apex] Replace Jorje with fully open source front-end
  • #4828: [apex] Support null coalescing operator ?? (apex 60)
  • #4845: [apex] Use same ANLTR version for apex-parser
• apex-bestpractices
  • #4556: [apex] UnusedLocalVariable flags for variables which are using in SOQL/SOSL binds
• apex-documentation
  • #4774: [apex] ApexDoc false-positive for the first method of an annotated Apex class
• apex-performance
  • #4675: [apex] New Rule: OperationWithHighCostInLoop
• groovy
  • #4726: [groovy] Support Groovy to 3 and 4 and CPD suppressions
• java
  • #1307: [java] AccessNode API changes
  • #3751: [java] Rename some node types
  • #4628: [java] Support loading classes from java runtime images
  • #4753: [java] PMD crashes while using generics and wildcards
  • #4757: [java] Intermittent NPEs while analyzing Java code
  • #4794: [java] Support JDK 22
• java-bestpractices
  • #4603: [java] UnusedAssignment false positive in record compact constructor
  • #4625: [java] UnusedPrivateMethod false positive: Autoboxing into Number
  • #4817: [java] UnusedPrivateMethod false-positive used in lambda
• java-codestyle
  • #2847: [java] New Rule: Use Explicit Types
  • #4239: [java] UnnecessaryLocalBeforeReturn - false positive with catch clause
  • #4578: [java] CommentDefaultAccessModifier comment needs to be before annotation if present
  • #4631: [java] UnnecessaryFullyQualifiedName fails to recognize illegal self reference in enums
  • #4645: [java] CommentDefaultAccessModifier - False Positive with JUnit5’s ParameterizedTest
  • #4754: [java] EmptyControlStatementRule: Add allowCommentedBlocks property
  • #4816: [java] UnnecessaryImport false-positive on generic method call with on lambda
• java-design
  • #174: [java] SingularField false positive with switch in method that both assigns and reads field
• java-errorprone
  • #718: [java] BrokenNullCheck false positive with parameter/field confusion
  • #932: [java] SingletonClassReturningNewInstance false positive with double assignment
  • #1831: [java] DetachedTestCase reports abstract methods
  • #4719: [java] UnnecessaryCaseChange: example doc toUpperCase() should compare to a capitalized string
• javascript
  • #2305: [javascript] UnnecessaryBlock - false positives with destructuring assignments
  • #4673: [javascript] CPD: Added support for decorator notation
• plsql
  • #4820: [plsql] WITH clause is ignored for SELECT INTO statements
• swift
  • #4697: [swift] Support Swift 5.9 features (mainly macros expansion expressions)
• xml-bestpractices
  • #4592: [xml] Add MissingEncoding rule

API Changes

See Detailed Release Notes for PMD 7.

External Contributions

• #4093: [apex] Summit-AST Apex module - Part 1 - Edward Klimoshenko (@eklimo)
• #4151: [apex] Summit-AST Apex module - Part 2 - expression nodes - Aaron Hurst (@aaronhurst-google)
• #4171: [apex] Summit-AST Apex module - Part 3 - initializers - Aaron Hurst (@aaronhurst-google)
• #4206: [apex] Summit-AST Apex module - Part 4 - statements - Aaron Hurst (@aaronhurst-google)
• #4219: [apex] Summit-AST Apex module - Part 5 - annotations, triggers, misc. - Aaron Hurst (@aaronhurst-google)
• #4242: [apex] Merge 6.52 into experimental-apex-parser - Aaron Hurst (@aaronhurst-google)
• #4251: [apex] Summit-AST Apex module - Part 6 Passing testsuite - Aaron Hurst (@aaronhurst-google)
• #4448: [apex] Bump summit-ast to new release 2.1.0 (and remove workaround) - Aaron Hurst (@aaronhurst-google)
• #4479: [apex] Merge main (7.x) branch into experimental-apex-parser and fix tests - Aaron Hurst (@aaronhurst-google)
• #4562: [apex] Fixes #4556 - Update Apex bind regex match for all possible combinations - nwcm (@nwcm)
• #4640: [cli] Launch script fails if run via “bash pmd” - Shai Bennathan (@shai-bennathan)
• #4673: [javascript] CPD: Added support for decorator notation - Wener (@wener-tiobe)
• #4677: [apex] Add new rule: OperationWithHighCostInLoop - Thomas Prouvot (@tprouvot)
• #4698: [swift] Add macro expansion support for swift 5.9 - Richard B. (@kenji21)
• #4706: [java] DetachedTestCase should not report on abstract methods - Debamoy Datta (@Debamoy)
• #4719: [java] UnnecessaryCaseChange: example doc toUpperCase() should compare to a capitalized string - ciufudean (@ciufudean)
• #4738: [doc] Added reference to the PMD extension for bld - Erik C. Thauvin (@ethauvin)
• #4749: Fixes NoSuchMethodError on processing errors in pmd-compat6 - Andreas Bergander (@bergander)
• #4750: [core] Fix flaky SummaryHTMLRenderer - 219sansim (@219sansim)
• #4752: [core] Fix flaky LatticeRelationTest - 219sansim (@219sansim)
• #4754: [java] EmptyControlStatementRule: Add allowCommentedBlocks property - Andreas Bergander (@bergander)
• #4759: [java] fix: remove delimiter attribute from ruleset category/java/errorprone.xml - Marcin Dąbrowski (@marcindabrowski)
• #4825: [plsql] Fix ignored WITH clause for SELECT INTO statements - Laurent Bovet (@lbovet)
• #4857: [javascript] Fix UnnecessaryBlock issues with empty statements - Oleksandr Shvets (@oleksandr-shvets)

🚀 Major Features and Enhancements

New official logo

The new official logo of PMD:

For more information, see the Detailed Release Notes for PMD 7.

Revamped Java module

• Java grammar substantially refactored - more correct regarding the Java Language Specification (JLS)
• Built-in rules have been upgraded for the changed AST
• Rewritten type resolution framework and symbol table correctly implements the JLS
• AST exposes more semantic information (method calls, field accesses)

For more information, see the Detailed Release Notes for PMD 7.

Contributors: Clément Fournier (@oowekyala), Andreas Dangel (@adangel), Juan Martín Sotuyo Dodero (@jsotuyod)

Revamped Command Line Interface

• Unified and consistent Command Line Interface for both Linux/Unix and Windows across our different utilities
• Single script pmd (pmd.bat for Windows) to launch the different utilities:
  • pmd check to run PMD rules and analyze a project
  • pmd cpd to run CPD (copy paste detector)
  • pmd designer to run the PMD Rule Designer
• Progress bar support for pmd check
• Shell completion

For more information, see the Detailed Release Notes for PMD 7.

Contributors: Juan Martín Sotuyo Dodero (@jsotuyod)

Full Antlr support

• Antlr based grammars can now be used to build full-fledged PMD rules.
• Previously, Antlr grammar could only be used for CPD
• New supported languages: Swift and Kotlin

For more information, see the Detailed Release Notes for PMD 7.

Contributors: Lucas Soncini (@lsoncini), Matías Fraga (@matifraga), Tomás De Lucca (@tomidelucca)

Updated PMD Designer

This PMD release ships a new version of the pmd-designer. The designer artifact has been renamed from “pmd-ui” to “pmd-designer”. While the designer still works with Java 8, the recommended Java Runtime is Java 11 (or later) with OpenJFX 17 (or later).

For the detailed changes, see

• PMD Designer Changelog (7.0.0).
• PMD Designer Changelog (7.0.0-rc4).
• PMD Designer Changelog (7.0.0-rc1).

New CPD report format cpdhtml-v2.xslt

Thanks to @mohan-chinnappan-n a new CPD report format has been added which features a data table. It uses an XSLT stylesheet to convert CPD’s XML format into HTML.

See the example report.

Contributors: Mohan Chinnappan (@mohan-chinnappan-n)

🎉 Language Related Changes

Note that this is just a concise listing of the highlights. For more information on the languages, see the Detailed Release Notes for PMD 7.

New: CPD support for Apache Velocity Template Language (VTL)

PMD supported Apache Velocity for a very long time, but the CPD integration never got finished. This is now done and CPD supports Apache Velocity Template language for detecting copy and paste. It is shipped in the module pmd-velocity.

New: CPD support for Coco

Thanks to a contribution, CPD now supports Coco, a modern programming language designed specifically for building event-driven software. It is shipped in the new module pmd-coco.

Contributors: Wener (@wener-tiobe)

New: CPD support for Julia

Thanks to a contribution, CPD now supports the Julia language. It is shipped in the new module pmd-julia.

Contributors: Wener (@wener-tiobe)

New: CPD support for TypeScript

Thanks to a contribution, CPD now supports the TypeScript language. It is shipped with the rest of the JavaScript support in the module pmd-javascript.

Contributors: Paul Guyot (@pguyot)

New: Java 21 and 22 Support

This release of PMD brings support for Java 21 and 22. There are the following new standard language features, that are supported now:

• JEP 456: Unnamed Variables & Patterns (Java 22)
• JEP 440: Record Patterns (Java 21)
• JEP 441: Pattern Matching for switch (Java 21)

PMD also supports the following preview language features:

• JEP 447: Statements before super(…) (Preview) (Java 22)
• JEP 459: String Templates (Second Preview) (Java 21 and 22)
• JEP 463: Implicitly Declared Classes and Instance Main Methods (Second Preview) (Java 21 and 22)

In order to analyze a project with PMD that uses these preview language features, you’ll need to enable it via the environment variable PMD_JAVA_OPTS and select the new language version 22-preview:

export PMD_JAVA_OPTS=--enable-preview
pmd check --use-version java-22-preview ...

Note: Support for Java 19 and Java 20 preview language features have been removed. The versions “19-preview” and “20-preview” are no longer available.

New: Kotlin support

• Use PMD to analyze Kotlin code with PMD rules.
• Support for Kotlin 1.8 grammar
• Initially 2 built-in rules
• Support for Kotlin was introduced with PMD 7.0.0-rc1 as an experimental feature. With PMD 7.0.0 this is now considered stable.

Contributors: Jeroen Borgers (@jborgers), Peter Paul Bakker (@stokpop)

New: Swift support

• Use PMD to analyze Swift code with PMD rules.
• Limited support for Swift 5.9 (Macro Expansions)
• Initially 4 built-in rules

Contributors: Lucas Soncini (@lsoncini), Matías Fraga (@matifraga), Tomás De Lucca (@tomidelucca)

Changed: Apex Support: Replaced Jorje with fully open source front-end

When PMD added Apex support with version 5.5.0, it utilized the Apex Jorje library to parse Apex source and generate an AST. This library is however a binary-blob provided as part of the Salesforce Extensions for VS Code, and it is closed-source.

This causes problems, if binary blobs are not allowed by e.g. a company-wide policy. In that case, the Jorje library prevented that PMD Apex could be used at all.

Also having access to the source code, enhancements and modifications are easier to do.

Under the hood, we use two open source libraries instead:

• apex-parser by Kevin Jones (@nawforce) This project provides the grammar for a ANTLR based parser.
• Summit-AST by Google (@google) This project translates the ANTLR parse tree into an AST, that is similar to the AST Jorje provided. Note: This is not an official Google product.

Although the parsers is completely switched, there are only little known changes to the AST. These are documented in the Migration Guide for PMD 7: Apex AST. With the new Apex parser, the new language constructs like User Mode Database Operations and the new Null Coalescing Operator ?? can be parsed now. PMD should be able to parse Apex code up to version 60.0 (Spring ‘24).

See #3766 for details.

Contributors: Aaron Hurst (@aaronhurst-google), Edward Klimoshenko (@eklimo)

Changed: CPP can now ignore identifiers in sequences (CPD)

• New command line option for CPD: --ignore-sequences.
• This option is used for CPP only: with the already existing option --ignore-literal-sequences, only literals were ignored. The new option additionally ignores identifiers as well in sequences.
• See PR #4470 for details.

Contributors: Wener (@wener-tiobe)

Changed: Groovy Support (CPD)

• We now support parsing all Groovy features from Groovy 3 and 4.
• We now support suppression through CPD-ON/CPD-OFF comment pairs.
• See PR #4726 for details.

Contributors: Juan Martín Sotuyo Dodero (@jsotuyod)

Changed: HTML support

Support for HTML was introduced in PMD 6.55.0 as an experimental feature. With PMD 7.0.0 this is now considered stable.

Changed: JavaScript support

• Latest version supports ES6 and also some new constructs (see Rhino)
• Comments are retained

Changed: Language versions

• More predefined language versions for each supported language
• Can be used to limit rule execution for specific versions only with minimumLanguageVersion and maximumLanguageVersion attributes.

Changed: Rule properties

• The old deprecated classes like IntProperty and StringProperty have been removed. Please use PropertyFactory to create properties.
• All properties which accept multiple values now use a comma (,) as a delimiter. The previous default was a pipe character (|). The delimiter is not configurable anymore. If needed, the comma can be escaped with a backslash.
• The min and max attributes in property definitions in the XML are now optional and can appear separately or be omitted.

Changed: Velocity Template Language (VTL)

The module was named just “vm” which was not a good name. Its module name, language id and package names have been renamed to “velocity”.

If you import rules, you also need to adjust the paths, e.g.

• category/vm/... ➡️ category/velocity/...

Changed: Visualforce

There was an inconsistency between the naming of the maven module and the language id. The language id used the abbreviation “vf”, while the maven module used the longer name “visualforce”. This has been solved by renaming the language module to its full name “visualforce”. The java packages have been renamed as well.

If you import rules, you also need to adjust the paths, e.g.

• category/vf/security.xml ➡️ category/visualforce/security.xml

🌟 New and changed rules

New Rules

Apex

• OperationWithHighCostInLoop finds Schema class methods called in a loop, which is a potential performance issue.
• UnusedMethod finds unused methods in your code.

Java

• UnnecessaryBoxing reports boxing and unboxing conversions that may be made implicit.
• UseExplicitTypes reports usages of var keyword, which was introduced with Java 10.

Kotlin

• FunctionNameTooShort finds functions with a too short name.
• OverrideBothEqualsAndHashcode finds classes with only either equals or hashCode overridden, but not both. This leads to unexpected behavior once instances of such classes are used in collections (Lists, HashMaps, …).

Swift

• ForceCast flags all force casts, making sure you are defensively considering all types. Having the application crash shouldn’t be an option.
• ForceTry flags all force tries, making sure you are defensively handling exceptions. Having the application crash shouldn’t be an option.
• ProhibitedInterfaceBuilder flags any usage of interface builder. Interface builder files are prone to merge conflicts, and are impossible to code review, so larger teams usually try to avoid it or reduce its usage.
• UnavailableFunction flags any function throwing a fatalError not marked as @available(*, unavailable) to ensure no calls are actually performed in the codebase.

XML

• MissingEncoding finds XML files without explicit encoding.

Other changes

The information about changed rules, removed rules and rulesets can be found in the Detailed Release Notes for PMD 7.

🚨 API

The API of PMD has been growing over the years and needed some cleanup. The goal is, to have a clear separation between a well-defined API and the implementation, which is internal. This should help us in future development.

Also, there are some improvement and changes in different areas. For the detailed description of the changes listed here, see Detailed Release Notes for PMD 7.

• Miscellaneous smaller changes and cleanups
• XPath 3.1 support for XPath-based rules
• Node stream API for AST traversal
• Metrics framework
• Testing framework
• Language Lifecycle and Language Properties
• Rule Properties
• New Programmatic API for CPD

💥 Compatibility and migration notes

A detailed documentation of required changes are available in the Migration Guide for PMD 7.

See also Detailed Release Notes for PMD 7.

🐛 Fixed Issues

More than 300 issues have been fixed in PMD 7. See Detailed Release Notes for PMD 7 for the complete list of fixed issues.

✨ External Contributions

Many thanks to the following contributors: @219sansim, @aaronhurst-google, @anastasiia-koba, @AndreyBozhko, @bergander, @ciufudean, @cyw3, @dague1, @Debamoy, @eklimo, @ethauvin, @JerritEic, @joaodinissf, @kenji21, @krdabrowski, @lbovet, @lsoncini, @LynnBroe, @marcindabrowski, @matifraga, @mohan-chinnappan-n, @mohui1999, @nawforce, @nirvikpatel, @nwcm, @oleksandr-shvets, @pguyot, @PimvanderLoos, @rcorfieldffdc, @sfdcsteve, @shai-bennathan, @tomidelucca, @tprouvot, @wener-tiobe.

See Detailed Release Notes for PMD 7 for the full list of PRs.

📈 Stats

• 5741 commits
• 849 closed tickets & PRs
• Days since last release (6.55.0): 390
• Days since last release (7.0.0-rc4): 173