hiifong/pmd
1
0
Fork 0
forked from phoedos/pmd
Code Pull Requests Activity

Update release notes, fix typos

Browse Source
This commit is contained in:
Andreas Dangel
2018-07-29 10:39:03 +02:00
parent c598d3b049
commit 7e737b3c8a
2 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/pages/release_notes.md
View File

@ -22,14 +22,15 @@ This is a minor release.
#### New Rules
* The new Java rule [`LocalVariableNamingConventions`](pmd_rules_java_codestyle.html#localvariablenamingconventions) (`java-codestlye`)
detects local variable names that don't comply to a given convention. It defaults to standrd Java convention of using camelCase,
but can be configured. Special cases can be configured for final variables and catched exceptions' names.
* The new Java rule [`LocalVariableNamingConventions`](pmd_rules_java_codestyle.html#localvariablenamingconventions)
(`java-codestyle`) detects local variable names that don't comply to a given convention. It defaults to standard
Java convention of using camelCase, but can be configured. Special cases can be configured for final variables
and caught exceptions' names.
* The new Java rule [`FormalParameterNamingConventions`](pmd_rules_java_codestyle.html#formalparameternamingconventions) (`java-codestlye`)
detects formal parameter names that don't comply to a given convention. It defaults to standrd Java convention of using camelCase,
but can be configured. Special cases can be configured for final parameters and lambda parameters (considering wether they are
explicitly typed or not)
* The new Java rule [`FormalParameterNamingConventions`](pmd_rules_java_codestyle.html#formalparameternamingconventions)
(`java-codestyle`) detects formal parameter names that don't comply to a given convention. It defaults to
standard Java convention of using camelCase, but can be configured. Special cases can be configured for final
parameters and lambda parameters (considering whether they are explicitly typed or not).
### Fixed Issues
@ -49,8 +50,9 @@ This is a minor release.
### API Changes
* The `findDescendantsOfType` methods in `net.sourceforge.pmd.lang.ast.AbstractNode` no longer search for exact type matches, but will
match subclasses too. That means, it's now possible to look for abstract node types such as `AbstractJavaTypeNode` and not only for it's concrete subtypes.
* The `findDescendantsOfType` methods in `net.sourceforge.pmd.lang.ast.AbstractNode` no longer search for
exact type matches, but will match subclasses, too. That means, it's now possible to look for abstract node
types such as `AbstractJavaTypeNode` and not only for it's concrete subtypes.
### External Contributions

2
pmd-core/src/main/resources/rulesets/releases/660.xml
View File

@ -1,6 +1,6 @@
<?xml version="1.0"?>
<ruleset name="650"
<ruleset name="660"
xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0 http://pmd.sourceforge.net/ruleset_2_0_0.xsd">