From 7d9fd61c500774c0c0a693bff2531da0e6f45185 Mon Sep 17 00:00:00 2001 From: Andreas Dangel Date: Tue, 7 Aug 2018 19:17:21 +0200 Subject: [PATCH] Fix wrong merge --- docs/pages/release_notes.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/pages/release_notes.md b/docs/pages/release_notes.md index 57b8a0c653..f68a7a8d78 100644 --- a/docs/pages/release_notes.md +++ b/docs/pages/release_notes.md @@ -27,15 +27,6 @@ This is a minor release. Besides method names, the rule also checks field and variable names. It also checks, that getters return something but setters won't. The rule has several properties with which it can be customized. -* 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 [`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 PL/SQL rule [`ForLoopNaming`](pmd_rules_plsql_codestyle.html#forloopnaming) (`plsql-codestyle`) enforces a naming convention for "for loops". Both "cursor for loops" and "index for loops" are covered. The rule can be customized via patterns. By default, short variable names are reported.