Merge branch 'pr-2617'

[core] Deprecate missing language attribute on rule definition #2617
This commit is contained in:
Andreas Dangel
2020-07-30 10:19:03 +02:00
32 changed files with 244 additions and 14 deletions

View File

@@ -120,6 +120,11 @@ Example:
</rule>
```
{% include note.html content="In PMD 7, the `language` attribute will be required on all `rule`
elements that declare a new rule. Some base rule classes set the language implicitly in their
constructor, and so this is not required in all cases for the rule to work. But this
behavior will be discontinued in PMD 7, so missing `language` attributes are
reported beginning with PMD 6.27.0 as a forward compatibility warning." %}
## Resource index

View File

@@ -16,11 +16,19 @@ This is a {{ site.pmd.release_type }} release.
### Fixed Issues
* core
* [#724](https://github.com/pmd/pmd/issues/724): \[core] Avoid parsing rulesets multiple times
* java-performance
* [#2441](https://github.com/pmd/pmd/issues/2441): \[java] RedundantFieldInitializer can not detect a special case for char initialize: `char foo = '\0';`
### API Changes
* XML rule definition in rulesets: In PMD 7, the `language` attribute will be required on all `rule`
elements that declare a new rule. Some base rule classes set the language implicitly in their
constructor, and so this is not required in all cases for the rule to work. But this
behavior will be discontinued in PMD 7, so missing `language` attributes are now
reported as a forward compatibility warning.
### External Contributions
* [#2677](https://github.com/pmd/pmd/pull/2677): \[java] RedundantFieldInitializer can not detect a special case for char initialize: `char foo = '\0';` - [Mykhailo Palahuta](https://github.com/Drofff)