29 April 2018
The PMD team is pleased to announce PMD 6.3.0.
This is a minor release.
As described in #904, when searching for child nodes of the AST methods
findDescendantsOfType were found to behave inconsistently,
not all of them honoring find boundaries; that is, nodes that define a self-contained entity which should be considered separately
(think of lambdas, nested classes, anonymous classes, etc.). We have modified these methods to ensure all of them honor
This change implies several false positives / unexpected results
ASTBlockStatement falsely returning
have been fixed; and lots of searches are now restricted to smaller search areas, which improves performance
(depending on the project, we have measured up to 10% improvements during Type Resolution, Symbol Table analysis,
and some rules’ application).
has been enhanced to allow granular configuration of naming
conventions for different kinds of type declarations (eg enum or abstract
class). Each kind of declaration can use its own naming convention
using a regex property. See the rule’s documentation for more info about
configuration and default conventions.
has been enhanced in the same way.
Back in PMD 5.6.0 we introduced the ability to suppress CPD warnings in Java using comments, by
CPD-OFF (to start ignoring code), or
CPD-ON (to resume analysis) during CPD execution.
This has proved to be much more flexible and versatile than the old annotation-based approach,
and has since been the preferred way to suppress CPD warnings.
On this occasion, we are extending support for comment-based suppressions to many other languages:
So for instance, in Python we could now do:
class BaseHandler(object): def __init__(self): # some unignored code # tell cpd to start ignoring code - CPD-OFF # mission critical code, manually loop unroll GoDoSomethingAwesome(x + x / 2); GoDoSomethingAwesome(x + x / 2); GoDoSomethingAwesome(x + x / 2); GoDoSomethingAwesome(x + x / 2); GoDoSomethingAwesome(x + x / 2); GoDoSomethingAwesome(x + x / 2); # resume CPD analysis - CPD-ON # further code will *not* be ignored
Other languages are equivalent.
Thanks to major contributions from kenji21 the Swift grammar has been updated to support Swift 4.1. This is a major update, since the old grammar was quite dated, and we are sure all iOS developers will enjoy it.
Unfortunately, this change is not compatible. The grammar elements that have been removed (ie: the keywords
__FUNCTION__) are no longer supported. We don’t usually introduce such
drastic / breaking changes in minor releases, however, given that the whole Swift ecosystem pushes hard towards
always using the latest versions, and that Swift needs all code and libraries to be currently compiling against
the same Swift version, we felt strongly this change was both safe and necessary to be shipped as soon as possible.
We had great feedback from the community during the process but if you have a legitimate use case for older Swift
versions, please let us know on our Issue Tracker.
java-security) detects hard coded initialization vectors used in cryptographic operations. It is recommended to use a randomly generated IV.
The Java rule UnnecessaryConstructor (
has been rewritten as a Java rule (previously it was a XPath-based rule). It supports a new property
ignoredAnnotations and ignores by default empty constructors,
that are annotated with
javax.inject.Inject. Additionally, it detects now also unnecessary private constructors
checkNativeMethods of the Java rule MethodNamingConventions (
is now deprecated, as it is now superseded by
nativePattern. Support for that property will be maintained until
The Java rule ControlStatementBraces (
supports a new boolean property
checkSingleIfStmt. When unset, the rule won’t report
if statements which lack
braces, if the statement is not part of an
if ... else if chain. This property defaults to true.
java-codestyle) is deprecated in favour of ClassNamingConventions. See Naming rules enhancements.