Merge branch 'pr-1745'

This commit is contained in:
Andreas Dangel
2019-04-01 19:31:07 +02:00
6 changed files with 9 additions and 7 deletions

View File

@ -7,7 +7,7 @@ author: Binguo Bao <djydewang@gmail.com>
## Introduction
Pmdtester is a regression testing tool that ensures no new problems and unexpected behaviors will be introduced to PMD after fixing an issue.
It can also be used to verify, that new rules work as expected.It has been integrated into travis CI and is actually used automatically for PRs.
It can also be used to verify, that new rules work as expected. It has been integrated into travis CI and is actually used automatically for PRs.
Regression difference reports are commented back to the PR for the reviewer's information e.g. https://github.com/pmd/pmd/pull/1265#issuecomment-408945709
## Run pmdtester locally

View File

@ -53,7 +53,7 @@ author: Tom Copeland <tom@infoether.org>
* Pieter Vanraemdonck - JSP grammar/integration/documentation, DontNestJsfInJstlIteration, NoLongScripts,
NoScriptlets, NoInlineStyleInformation, NoClassAttribute, NoJspForward
* Raik Schroeder - data flow analyis layer, YAHTMLRenderer
* Raik Schroeder - data flow analysis layer, YAHTMLRenderer
* Steve Hawkins - rewrite of CPD based on Karp-Rabin string matching
* Daniel Sheppard - XPath engine integration concept and implementation, advice on Jaxen extension function naming
* Brian Ewins - complete rewrite of CPD based on the Burrows-Wheeler transform, fixed DocumentNavigator bug
@ -78,7 +78,7 @@ author: Tom Copeland <tom@infoether.org>
* Jeff Campbell - Found bug and suggested fix for problem with XMLRenderer and SuppressWarnings("PMD") annotations
* Kris Jurka - CPD patch to accept ".C" as a filename extension for C/C++ files
* Florian Deissenboeck - reported several Java 1.5 grammar bugs
* Maarten ter Huurne - BooleanGetMethodName, AddEmptyString, Noticed mispeling in AvoidArrayLoops rule
* Maarten ter Huurne - BooleanGetMethodName, AddEmptyString, Noticed misspelling in AvoidArrayLoops rule
* Lukas Theussl - Patch to bring Maven configuration files up to date
* Jason Bennett - Rewrite of annotation-based warning suppression to allow for rule-specific suppression,
noticed useless line in XSLT scripts, fix for UnnecessaryLocalBeforeReturn, wrote NPathComplexity rule,
@ -143,7 +143,7 @@ author: Tom Copeland <tom@infoether.org>
reported mistake in UnnecessaryLocalBeforeReturn message,
bug report 1371757 for misleading AvoidSynchronizedAtMethodLevel example,
bug report 1293277 for duplicated rule messages, bug report for ConstructorCallsOverridableMethod,
suggestion for improving command line interface, mispeling report, suggestion for improving Designer
suggestion for improving command line interface, misspelling report, suggestion for improving Designer
startup script, "how to make a ruleset" documentation suggestions, noticed outdated Xerces jars,
script renaming suggestions, UseLocaleWithCaseConversions rule suggestion
* David Karr - reported stale XPath documentation

View File

@ -54,7 +54,7 @@ Properties are assigned a value with a `property` element, which should mention
<property name="reportLevel" value="150"/>
```
All property assignements must be enclosed in a `properties` element, which is itself inside a `rule` element.
All property assignments must be enclosed in a `properties` element, which is itself inside a `rule` element.
{%include tip.html content="The properties of a rule are documented with the rule, e.g. [here](pmd_rules_java_design.html#npathcomplexity) for NPathComplexity. Note that **assigning a value to a property that does not exist throws an error!**" %}

View File

@ -391,7 +391,7 @@ Additionally, **Java** allows to toggle suppression by adding the annotations
all code within will be ignored by CPD.
This approach however, is limited to the locations were `@SuppressWarnings` is accepted.
It's legacy and the new comment's based approch should be favored.
It's legacy and the new comment's based approach should be favored.
```java
//enable suppression

View File

@ -16,7 +16,7 @@ analysis time dramatically.
The generated report will be *exactly the same* as it would if running without incremental analysis.
Files included in the final report will reflect exactly those files in your filesystem. Even if
untouched, files with violations will be listed with full detail. Therefore, its usage is higly recommended.
untouched, files with violations will be listed with full detail. Therefore, its usage is highly recommended.
### Enabling incremental analysis

View File

@ -20,5 +20,7 @@ This is a {{ site.pmd.release_type }} release.
### External Contributions
* [#1745](https://github.com/pmd/pmd/pull/1745): \[doc] Fixed some errors in docs - [0xflotus](https://github.com/0xflotus)
{% endtocmaker %}