dependabot maven(deps): bump pmd.version from 7.6.0 to 7.7.0
Bumps pmd.version
from 7.6.0 to 7.7.0.
Updates pmd-core
from 7.6.0 to 7.7.0
Release notes
Sourced from pmd-core's releases.
PMD 7.7.0 (25-October-2024)
25-October-2024 - 7.7.0
The PMD team is pleased to announce PMD 7.7.0.
This is a minor release.
Table Of Contents
🚀 New and noteworthy🌟 Rule Changes🐛 Fixed Issues🚨 API Changes✨ Merged pull requests📦 Dependency updates📈 Stats
🚀 New and noteworthyCPD can now ignore literals and identifiers in C++ code
When searching for duplicated code in C++ differences in literals or identifiers can be ignored now (like in Java). This can be enabled via the command line options
--ignore-literal
and--ignore-identifiers
.
See [PR #5040](pmd/pmd#5040) for details.
🌟 Rule ChangesChanged Rules
SwitchStmtsShouldHaveDefault
(Java Best Practices) doesn't report empty switch statements anymore. To detect these, useEmptyControlStatement
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.TooFewBranchesForSwitch
(Java Performance) doesn't report empty switches anymore. To detect these, useEmptyControlStatement
.Renamed Rules
- Several rules for unit testing have been renamed to better reflect their actual scope. Lots of them were called after JUnit / JUnit 4, even when they applied to JUnit 5 and / or TestNG.
UnitTestAssertionsShouldIncludeMessage
(Java Best Practices) has been renamed fromJUnitAssertionsShouldIncludeMessage
.UnitTestContainsTooManyAsserts
(Java Best Practices) has been renamed fromJUnitTestContainsTooManyAsserts
.UnitTestShouldIncludeAssert
(Java Best Practices) has been renamed fromJUnitTestsShouldIncludeAssert
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseAfterAnnotation
.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseBeforeAnnotation
.UnitTestShouldUseTestAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseTestAnnotation
.- Several rules about switch statements and switch expression have been renamed, as they apply both to Switch Statements and to Switch Expressions:
... (truncated)
Commits
-
7739f2b
[release] prepare release pmd_releases/7.7.0 -
919e73f
Prepare pmd release 7.7.0 -
e2d59c0
Fix #5244: [java] UselessOperationOnImmutable: consider java.time.* types (#5... -
8f2d47d
Fix #5270: [apex] AvoidNonRestrictiveQueries: Fix regex for detecting LIMIT c... -
e6097d6
[java] Rename rule SwitchStmtsShouldHaveDefault to NonExhaustiveSwitch (#5267) -
5e83246
[doc] Update release notes (#5267) -
62c2858
Fix #5257: [java] NonCaseLabelInSwitch - support switch expressions (#5256) -
0d8878d
[java] Rename rule DefaultLabelNotLastInSwitch (#5255) -
4b23718
Fix #4813: [java] SwitchStmtsShouldHaveDefault false positive with pattern ma... -
3a501a0
Fix #5249 and #5250: [java] TooFewBranchesForSwitch ignore pattern matching a... - Additional commits viewable in compare view
Updates pmd-java
from 7.6.0 to 7.7.0
Release notes
Sourced from pmd-java's releases.
PMD 7.7.0 (25-October-2024)
25-October-2024 - 7.7.0
The PMD team is pleased to announce PMD 7.7.0.
This is a minor release.
Table Of Contents
🚀 New and noteworthy🌟 Rule Changes🐛 Fixed Issues🚨 API Changes✨ Merged pull requests📦 Dependency updates📈 Stats
🚀 New and noteworthyCPD can now ignore literals and identifiers in C++ code
When searching for duplicated code in C++ differences in literals or identifiers can be ignored now (like in Java). This can be enabled via the command line options
--ignore-literal
and--ignore-identifiers
.
See [PR #5040](pmd/pmd#5040) for details.
🌟 Rule ChangesChanged Rules
SwitchStmtsShouldHaveDefault
(Java Best Practices) doesn't report empty switch statements anymore. To detect these, useEmptyControlStatement
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.TooFewBranchesForSwitch
(Java Performance) doesn't report empty switches anymore. To detect these, useEmptyControlStatement
.Renamed Rules
- Several rules for unit testing have been renamed to better reflect their actual scope. Lots of them were called after JUnit / JUnit 4, even when they applied to JUnit 5 and / or TestNG.
UnitTestAssertionsShouldIncludeMessage
(Java Best Practices) has been renamed fromJUnitAssertionsShouldIncludeMessage
.UnitTestContainsTooManyAsserts
(Java Best Practices) has been renamed fromJUnitTestContainsTooManyAsserts
.UnitTestShouldIncludeAssert
(Java Best Practices) has been renamed fromJUnitTestsShouldIncludeAssert
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseAfterAnnotation
.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseBeforeAnnotation
.UnitTestShouldUseTestAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseTestAnnotation
.- Several rules about switch statements and switch expression have been renamed, as they apply both to Switch Statements and to Switch Expressions:
... (truncated)
Commits
-
7739f2b
[release] prepare release pmd_releases/7.7.0 -
919e73f
Prepare pmd release 7.7.0 -
e2d59c0
Fix #5244: [java] UselessOperationOnImmutable: consider java.time.* types (#5... -
8f2d47d
Fix #5270: [apex] AvoidNonRestrictiveQueries: Fix regex for detecting LIMIT c... -
e6097d6
[java] Rename rule SwitchStmtsShouldHaveDefault to NonExhaustiveSwitch (#5267) -
5e83246
[doc] Update release notes (#5267) -
62c2858
Fix #5257: [java] NonCaseLabelInSwitch - support switch expressions (#5256) -
0d8878d
[java] Rename rule DefaultLabelNotLastInSwitch (#5255) -
4b23718
Fix #4813: [java] SwitchStmtsShouldHaveDefault false positive with pattern ma... -
3a501a0
Fix #5249 and #5250: [java] TooFewBranchesForSwitch ignore pattern matching a... - Additional commits viewable in compare view
Updates pmd-javascript
from 7.6.0 to 7.7.0
Release notes
Sourced from pmd-javascript's releases.
PMD 7.7.0 (25-October-2024)
25-October-2024 - 7.7.0
The PMD team is pleased to announce PMD 7.7.0.
This is a minor release.
Table Of Contents
🚀 New and noteworthy🌟 Rule Changes🐛 Fixed Issues🚨 API Changes✨ Merged pull requests📦 Dependency updates📈 Stats
🚀 New and noteworthyCPD can now ignore literals and identifiers in C++ code
When searching for duplicated code in C++ differences in literals or identifiers can be ignored now (like in Java). This can be enabled via the command line options
--ignore-literal
and--ignore-identifiers
.
See [PR #5040](pmd/pmd#5040) for details.
🌟 Rule ChangesChanged Rules
SwitchStmtsShouldHaveDefault
(Java Best Practices) doesn't report empty switch statements anymore. To detect these, useEmptyControlStatement
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.TooFewBranchesForSwitch
(Java Performance) doesn't report empty switches anymore. To detect these, useEmptyControlStatement
.Renamed Rules
- Several rules for unit testing have been renamed to better reflect their actual scope. Lots of them were called after JUnit / JUnit 4, even when they applied to JUnit 5 and / or TestNG.
UnitTestAssertionsShouldIncludeMessage
(Java Best Practices) has been renamed fromJUnitAssertionsShouldIncludeMessage
.UnitTestContainsTooManyAsserts
(Java Best Practices) has been renamed fromJUnitTestContainsTooManyAsserts
.UnitTestShouldIncludeAssert
(Java Best Practices) has been renamed fromJUnitTestsShouldIncludeAssert
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseAfterAnnotation
.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseBeforeAnnotation
.UnitTestShouldUseTestAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseTestAnnotation
.- Several rules about switch statements and switch expression have been renamed, as they apply both to Switch Statements and to Switch Expressions:
... (truncated)
Commits
-
7739f2b
[release] prepare release pmd_releases/7.7.0 -
919e73f
Prepare pmd release 7.7.0 -
e2d59c0
Fix #5244: [java] UselessOperationOnImmutable: consider java.time.* types (#5... -
8f2d47d
Fix #5270: [apex] AvoidNonRestrictiveQueries: Fix regex for detecting LIMIT c... -
e6097d6
[java] Rename rule SwitchStmtsShouldHaveDefault to NonExhaustiveSwitch (#5267) -
5e83246
[doc] Update release notes (#5267) -
62c2858
Fix #5257: [java] NonCaseLabelInSwitch - support switch expressions (#5256) -
0d8878d
[java] Rename rule DefaultLabelNotLastInSwitch (#5255) -
4b23718
Fix #4813: [java] SwitchStmtsShouldHaveDefault false positive with pattern ma... -
3a501a0
Fix #5249 and #5250: [java] TooFewBranchesForSwitch ignore pattern matching a... - Additional commits viewable in compare view
Updates pmd-jsp
from 7.6.0 to 7.7.0
Release notes
Sourced from pmd-jsp's releases.
PMD 7.7.0 (25-October-2024)
25-October-2024 - 7.7.0
The PMD team is pleased to announce PMD 7.7.0.
This is a minor release.
Table Of Contents
🚀 New and noteworthy🌟 Rule Changes🐛 Fixed Issues🚨 API Changes✨ Merged pull requests📦 Dependency updates📈 Stats
🚀 New and noteworthyCPD can now ignore literals and identifiers in C++ code
When searching for duplicated code in C++ differences in literals or identifiers can be ignored now (like in Java). This can be enabled via the command line options
--ignore-literal
and--ignore-identifiers
.
See [PR #5040](pmd/pmd#5040) for details.
🌟 Rule ChangesChanged Rules
SwitchStmtsShouldHaveDefault
(Java Best Practices) doesn't report empty switch statements anymore. To detect these, useEmptyControlStatement
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) now also considers JUnit 5 and TestNG tests.TooFewBranchesForSwitch
(Java Performance) doesn't report empty switches anymore. To detect these, useEmptyControlStatement
.Renamed Rules
- Several rules for unit testing have been renamed to better reflect their actual scope. Lots of them were called after JUnit / JUnit 4, even when they applied to JUnit 5 and / or TestNG.
UnitTestAssertionsShouldIncludeMessage
(Java Best Practices) has been renamed fromJUnitAssertionsShouldIncludeMessage
.UnitTestContainsTooManyAsserts
(Java Best Practices) has been renamed fromJUnitTestContainsTooManyAsserts
.UnitTestShouldIncludeAssert
(Java Best Practices) has been renamed fromJUnitTestsShouldIncludeAssert
.UnitTestShouldUseAfterAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseAfterAnnotation
.UnitTestShouldUseBeforeAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseBeforeAnnotation
.UnitTestShouldUseTestAnnotation
(Java Best Practices) has been renamed fromJUnit4TestShouldUseTestAnnotation
.- Several rules about switch statements and switch expression have been renamed, as they apply both to Switch Statements and to Switch Expressions:
... (truncated)
Commits
-
7739f2b
[release] prepare release pmd_releases/7.7.0 -
919e73f
Prepare pmd release 7.7.0 -
e2d59c0
Fix #5244: [java] UselessOperationOnImmutable: consider java.time.* types (#5... -
8f2d47d
Fix #5270: [apex] AvoidNonRestrictiveQueries: Fix regex for detecting LIMIT c... -
e6097d6
[java] Rename rule SwitchStmtsShouldHaveDefault to NonExhaustiveSwitch (#5267) -
5e83246
[doc] Update release notes (#5267) -
62c2858
Fix #5257: [java] NonCaseLabelInSwitch - support switch expressions (#5256) -
0d8878d
[java] Rename rule DefaultLabelNotLastInSwitch (#5255) -
4b23718
Fix #4813: [java] SwitchStmtsShouldHaveDefault false positive with pattern ma... -
3a501a0
Fix #5249 and #5250: [java] TooFewBranchesForSwitch ignore pattern matching a... - Additional commits viewable in compare view