From 29affeedc4e115ddcd293780516e7fbebc672b72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment=20Fournier?= <clement.fournier@tu-dresden.de>
Date: Thu, 21 Mar 2024 19:04:38 +0100
Subject: [PATCH] Remove unnecessary property declarations

---
 .../src/main/resources/category/java/bestpractices.xml    | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/pmd-java/src/main/resources/category/java/bestpractices.xml b/pmd-java/src/main/resources/category/java/bestpractices.xml
index b91266e1f5..03ed6fd517 100644
--- a/pmd-java/src/main/resources/category/java/bestpractices.xml
+++ b/pmd-java/src/main/resources/category/java/bestpractices.xml
@@ -914,10 +914,6 @@ Customize the maximum number of assertions used by this Rule to suit your needs.
 This rule checks for JUnit4, JUnit5 and TestNG Tests, as well as methods starting with "test".
         </description>
         <priority>3</priority>
-        <properties>
-            <property name="extraAssertMethodNames" type="List[String]"
-                      description="Extra valid assertion methods names"/>
-        </properties>
         <example>
 <![CDATA[
 public class MyTestCase extends TestCase {
@@ -949,10 +945,6 @@ JUnit tests should include at least one assertion.  This makes the tests more ro
 with messages provide the developer a clearer idea of what the test does.
         </description>
         <priority>3</priority>
-        <properties>
-            <property name="extraAssertMethodNames" type="List[String]"
-                      description="Extra valid assertion methods names"/>
-        </properties>
         <example>
 <![CDATA[
 public class Foo extends TestCase {