From 0d65c2e6e6081f15c98addc9b54e61c9425572e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Cl=C3=A9ment=20Fournier?= <clement.fournier76@gmail.com>
Date: Thu, 19 Mar 2020 01:49:55 +0100
Subject: [PATCH] Add relevant property tag

---
 .../resources/category/apex/codestyle.xml     |  5 ++
 .../resources/category/apex/errorprone.xml    |  6 ++
 .../sourceforge/pmd/lang/rule/XPathRule.java  |  4 +-
 .../net/sourceforge/pmd/xml/j2ee.xml          |  9 +++
 .../test/resources/rulesets/dummy/basic.xml   |  4 +-
 .../resources/rulesets/ruledoctest/sample.xml |  3 +
 .../rulesets/ruledoctest/sample2.xml          |  1 +
 .../resources/category/java/bestpractices.xml | 22 +++++++
 .../resources/category/java/codestyle.xml     | 32 ++++++++++
 .../main/resources/category/java/design.xml   | 18 ++++++
 .../resources/category/java/documentation.xml |  4 +-
 .../resources/category/java/errorprone.xml    | 58 +++++++++++++++++++
 .../category/java/multithreading.xml          |  7 +++
 .../resources/category/java/performance.xml   | 13 +++++
 .../pmd/ant/classpathtest/ruleset.xml         |  1 +
 .../category/ecmascript/bestpractices.xml     |  4 ++
 .../category/ecmascript/codestyle.xml         |  9 +++
 .../category/ecmascript/errorprone.xml        |  3 +
 .../resources/category/jsp/bestpractices.xml  |  4 ++
 .../main/resources/category/jsp/design.xml    |  3 +
 .../resources/category/jsp/errorprone.xml     |  1 +
 .../main/resources/category/jsp/security.xml  |  1 +
 .../category/plsql/bestpractices.xml          |  1 +
 .../resources/category/plsql/codestyle.xml    |  2 +
 .../main/resources/category/plsql/design.xml  |  1 +
 .../resources/category/plsql/errorprone.xml   |  3 +
 .../main/resources/rulesets/dummy/basic.xml   |  3 +-
 .../src/main/resources/category/vm/design.xml |  1 +
 .../resources/category/pom/errorprone.xml     |  2 +
 .../resources/category/xml/errorprone.xml     |  1 +
 .../main/resources/category/xsl/codestyle.xml |  1 +
 .../resources/category/xsl/performance.xml    |  1 +
 32 files changed, 223 insertions(+), 5 deletions(-)

diff --git a/pmd-apex/src/main/resources/category/apex/codestyle.xml b/pmd-apex/src/main/resources/category/apex/codestyle.xml
index 72c22c83ce..e76d6ebb8a 100644
--- a/pmd-apex/src/main/resources/category/apex/codestyle.xml
+++ b/pmd-apex/src/main/resources/category/apex/codestyle.xml
@@ -45,6 +45,7 @@ from the rest.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -82,6 +83,7 @@ controlled from the rest.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -139,6 +141,7 @@ from the rest.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -248,6 +251,7 @@ can lead to quite messy code. This rule looks for several declarations on the sa
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -345,6 +349,7 @@ controlled from the rest.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-apex/src/main/resources/category/apex/errorprone.xml b/pmd-apex/src/main/resources/category/apex/errorprone.xml
index 17c9182938..f7a184678e 100644
--- a/pmd-apex/src/main/resources/category/apex/errorprone.xml
+++ b/pmd-apex/src/main/resources/category/apex/errorprone.xml
@@ -59,6 +59,7 @@ Avoid directly accessing Trigger.old and Trigger.new as it can lead to a bug. Tr
         </description>
         <priority>3</priority>
             <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -120,6 +121,7 @@ or reported.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -153,6 +155,7 @@ Empty If Statement finds instances where a condition is checked but nothing is d
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -186,6 +189,7 @@ Empty block statements serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -221,6 +225,7 @@ Avoid empty try or finally blocks - what's the point?
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -267,6 +272,7 @@ a while loop that does a lot in the exit expression, rewrite it to make it clear
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-core/src/main/java/net/sourceforge/pmd/lang/rule/XPathRule.java b/pmd-core/src/main/java/net/sourceforge/pmd/lang/rule/XPathRule.java
index 55257976f9..e725d652df 100644
--- a/pmd-core/src/main/java/net/sourceforge/pmd/lang/rule/XPathRule.java
+++ b/pmd-core/src/main/java/net/sourceforge/pmd/lang/rule/XPathRule.java
@@ -41,8 +41,8 @@ public class XPathRule extends AbstractRule {
 
     static {
         Map<String, String> tmp = new HashMap<>();
-        tmp.put(XPATH_1_0, XPATH_2_0);
-        tmp.put(XPATH_1_0_COMPATIBILITY, XPATH_2_0);
+        tmp.put(XPATH_1_0, XPATH_1_0);
+        tmp.put(XPATH_1_0_COMPATIBILITY, XPATH_1_0_COMPATIBILITY);
         tmp.put(XPATH_2_0, XPATH_2_0);
         XPATH_VERSIONS = Collections.unmodifiableMap(tmp);
     }
diff --git a/pmd-core/src/test/resources/net/sourceforge/pmd/xml/j2ee.xml b/pmd-core/src/test/resources/net/sourceforge/pmd/xml/j2ee.xml
index 607967f6fd..17443c62ab 100644
--- a/pmd-core/src/test/resources/net/sourceforge/pmd/xml/j2ee.xml
+++ b/pmd-core/src/test/resources/net/sourceforge/pmd/xml/j2ee.xml
@@ -20,6 +20,7 @@
    </description>
    <priority>3</priority>
       <properties>
+          <property name="version" value="2.0"/>
           <property name="xpath">
               <value>
 <![CDATA[
@@ -49,6 +50,7 @@ public class Foo {
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //TypeDeclaration/ClassOrInterfaceDeclaration
@@ -93,6 +95,7 @@ public class Foo {
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
@@ -137,6 +140,7 @@ public class Foo {
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
@@ -181,6 +185,7 @@ public class Foo {
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
@@ -225,6 +230,7 @@ public class Foo {
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
@@ -278,6 +284,7 @@ application server should stop the JVM.
      ]]></description>
     	<priority>3</priority>
     	<properties>
+    		<property name="version" value="2.0"/>
     		<property name="xpath">
     			<value><![CDATA[
 //Name[starts-with(@Image,'System.exit')]
@@ -308,6 +315,7 @@ behavior especially when instances are distributed by the container on several J
     	</description>
     	<priority>3</priority>
     	<properties>
+    		<property name="version" value="2.0"/>
     		<property name="xpath">
     			<value><![CDATA[
 //ClassOrInterfaceDeclaration[
@@ -355,6 +363,7 @@ public class SomeEJB extends EJBObject implements EJBLocalHome {
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
diff --git a/pmd-core/src/test/resources/rulesets/dummy/basic.xml b/pmd-core/src/test/resources/rulesets/dummy/basic.xml
index 6ca9798570..b51c87830f 100644
--- a/pmd-core/src/test/resources/rulesets/dummy/basic.xml
+++ b/pmd-core/src/test/resources/rulesets/dummy/basic.xml
@@ -29,6 +29,7 @@ Just for test
         <priority>3</priority>
         <example> </example>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //dummyNode
@@ -43,6 +44,7 @@ Just for test
         <priority>3</priority>
         <example> </example>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //DummyNode
@@ -51,4 +53,4 @@ Just for test
         </properties>
     </rule>
 
-</ruleset>
\ No newline at end of file
+</ruleset>
diff --git a/pmd-doc/src/test/resources/rulesets/ruledoctest/sample.xml b/pmd-doc/src/test/resources/rulesets/ruledoctest/sample.xml
index 44e2bb76fb..78591da860 100644
--- a/pmd-doc/src/test/resources/rulesets/ruledoctest/sample.xml
+++ b/pmd-doc/src/test/resources/rulesets/ruledoctest/sample.xml
@@ -57,6 +57,7 @@ Here might be &lt;script&gt;alert('XSS');&lt;/script&gt; as well. And "quotes".
        </description>
        <priority>3</priority>
        <properties>
+           <property name="version" value="2.0"/>
            <property name="xpath">
                <value>
 <![CDATA[
@@ -145,6 +146,7 @@ Avoid jumbled loop incrementers - its usually a mistake, and is confusing even i
      </description>
      <priority>3</priority>
      <properties>
+         <property name="version" value="2.0"/>
          <property name="xpath">
              <value>
  <![CDATA[
@@ -195,6 +197,7 @@ Just some description of a deprecated rule.
  </description>
  <priority>3</priority>
  <properties>
+     <property name="version" value="2.0"/>
      <property name="xpath">
          <value>
 <![CDATA[
diff --git a/pmd-doc/src/test/resources/rulesets/ruledoctest/sample2.xml b/pmd-doc/src/test/resources/rulesets/ruledoctest/sample2.xml
index 88f5e15c02..a91a7e6b1f 100644
--- a/pmd-doc/src/test/resources/rulesets/ruledoctest/sample2.xml
+++ b/pmd-doc/src/test/resources/rulesets/ruledoctest/sample2.xml
@@ -19,6 +19,7 @@ Avoid jumbled loop incrementers - its usually a mistake, and is confusing even i
      </description>
      <priority>3</priority>
      <properties>
+         <property name="version" value="2.0"/>
          <property name="xpath">
              <value>
 <![CDATA[
diff --git a/pmd-java/src/main/resources/category/java/bestpractices.xml b/pmd-java/src/main/resources/category/java/bestpractices.xml
index 7dd321aee1..c20bf5f165 100644
--- a/pmd-java/src/main/resources/category/java/bestpractices.xml
+++ b/pmd-java/src/main/resources/category/java/bestpractices.xml
@@ -23,6 +23,7 @@ directly) a protected constructor can be provided prevent direct instantiation.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -194,6 +195,7 @@ Avoid printStackTrace(); use a logger call instead.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -299,6 +301,7 @@ if held within objects with long lifetimes.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -377,6 +380,7 @@ better placed in classes or enums. See Effective Java, item 19.
         <priority>3</priority>
         <properties>
         <property name="ignoreIfHasMethods" type="Boolean" description="Whether to ignore constants in interfaces if the interface defines any methods" value="true"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -422,6 +426,7 @@ By convention, the default label should be the last label in a switch statement.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -541,6 +546,7 @@ the loop iterates over. By default this rule allows a regular 'for' loop with on
         <properties>
             <property name="maximumVariables" type="Integer"
                       description="A regular for statement will have 1 control variable" min="0" max="100" value="1"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//ForInit/LocalVariableDeclaration[count(VariableDeclarator) > $maximumVariables]</value>
             </property>
@@ -587,6 +593,7 @@ through the @RunWith(Suite.class) annotation.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -628,6 +635,7 @@ JUnit 5 introduced @AfterEach and @AfterAll annotations to execute methods after
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -672,6 +680,7 @@ JUnit 5 introduced @BeforeEach and @BeforeAll annotations to execute methods bef
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -716,6 +725,7 @@ In JUnit 5, one of the following annotations should be used for tests: @Test, @R
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -793,6 +803,7 @@ This rule checks for JUnit4, JUnit5 and TestNG Tests, as well as methods startin
         <priority>3</priority>
         <properties>
             <property name="maximumAsserts" type="Integer" min="1" max="1000" description="Maximum number of Asserts in a test method" value="1"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -981,6 +992,7 @@ can lead to quite messy code. This rule looks for several declarations on the sa
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1025,6 +1037,7 @@ can be avoided, they will just return false.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1069,6 +1082,7 @@ can be avoided, they will just return false.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1146,6 +1160,7 @@ Consider replacing Enumeration usages with the newer java.util.Iterator
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1180,6 +1195,7 @@ Consider replacing Hashtable usage with the newer java.util.Map if thread safety
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//Type/ReferenceType/ClassOrInterfaceType[@Image='Hashtable']</value>
             </property>
@@ -1206,6 +1222,7 @@ Consider replacing Vector usages with the newer java.util.ArrayList if expensive
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//Type/ReferenceType/ClassOrInterfaceType[@Image='Vector']</value>
             </property>
@@ -1267,6 +1284,7 @@ will (and by priority) and avoid clogging the Standard out log.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1414,6 +1432,7 @@ This rule detects JUnit assertions in object equality. These assertions should b
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1460,6 +1479,7 @@ more specific methods, like assertNull, assertNotNull.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1509,6 +1529,7 @@ by more specific methods, like assertSame, assertNotSame.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1554,6 +1575,7 @@ When asserting a value is the same as a literal or Boxed boolean, use assertTrue
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-java/src/main/resources/category/java/codestyle.xml b/pmd-java/src/main/resources/category/java/codestyle.xml
index 1cb7beabeb..47030d6d0e 100644
--- a/pmd-java/src/main/resources/category/java/codestyle.xml
+++ b/pmd-java/src/main/resources/category/java/codestyle.xml
@@ -24,6 +24,7 @@ by {% rule java/codestyle/ClassNamingConventions %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -112,6 +113,7 @@ If the goal is to avoid defining constants in a scope smaller than the class, th
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -157,6 +159,7 @@ by the more general rule {% rule java/codestyle/FormalParameterNamingConventions
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -210,6 +213,7 @@ Clarify your intent by using private or package access modifiers instead.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -277,6 +281,7 @@ and increases the maintenance burden.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//Name[starts-with(@Image,'System.loadLibrary')]</value>
             </property>
@@ -314,6 +319,7 @@ prefix for these methods.
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -350,6 +356,7 @@ another constructor (such as an overloaded constructor) is called, this rule wil
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -550,6 +557,7 @@ The rule allows methods and fields annotated with Guava's @VisibleForTesting.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -621,6 +629,7 @@ usage by developers who should be implementing their own versions in the concret
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -667,6 +676,7 @@ public abstract class ShouldBeAbstract {
         <description>No need to explicitly extend Object.</description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -759,6 +769,7 @@ Some for loops can be simplified to while loops, this makes them more concise.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -799,6 +810,7 @@ by the rule {% rule java/codestyle/ControlStatementBraces %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//ForStatement[not(Statement/Block)]</value>
             </property>
@@ -861,6 +873,7 @@ Names for references to generic values should be limited to a single uppercase l
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -944,6 +957,7 @@ by the rule {% rule java/codestyle/ControlStatementBraces %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -986,6 +1000,7 @@ by the rule {% rule java/codestyle/ControlStatementBraces %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1082,6 +1097,7 @@ The Local Home interface of a Session EJB should be suffixed by 'LocalHome'.
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1120,6 +1136,7 @@ The Local Interface of a Session EJB should be suffixed by 'Local'.
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1215,6 +1232,7 @@ Fields, formal arguments, or local variable names that are too long can make the
         <priority>3</priority>
         <properties>
             <property name="minimum" type="Integer" description="The variable length reporting threshold" min="1" max="100" value="17"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1249,6 +1267,7 @@ The EJB Specification states that any MessageDrivenBean or SessionBean should be
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1340,6 +1359,7 @@ by the more general rule
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1479,6 +1499,7 @@ Detects when a package definition contains uppercase characters.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//PackageDeclaration/Name[lower-case(@Image)!=@Image]</value>
             </property>
@@ -1532,6 +1553,7 @@ Remote Interface of a Session EJB should not have a suffix.
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1578,6 +1600,7 @@ A Remote Home interface type of a Session EJB should be suffixed by 'Home'.
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1617,6 +1640,7 @@ Short Classnames with fewer than e.g. five characters are not recommended.
         <priority>4</priority>
         <properties>
             <property name="minimum" type="Integer" value="5" min="1" max="100" description="Number of characters that are required as a minimum for a class name."/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1645,6 +1669,7 @@ Method names that are very short are not helpful to the reader.
         <priority>3</priority>
         <properties>
             <property name="minimum" type="Integer" value="3" min="1" max="100" description="Number of characters that are required as a minimum for a method name."/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1726,6 +1751,7 @@ by the more general rule {% rule java/codestyle/FieldNamingConventions %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1765,6 +1791,7 @@ which class a static member comes from (Sun 1.5 Language Guide).
         <properties>
             <property name="maximumStaticImports" type="Integer"
                       description="All static imports can be disallowed by setting this to 0" min="0" max="100" value="4"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1968,6 +1995,7 @@ which makes the code also more readable.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <![CDATA[
@@ -2001,6 +2029,7 @@ List<String> stringsWithDiamond = new ArrayList<>(); // using the diamond operat
         <description>Useless parentheses should be removed.</description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2089,6 +2118,7 @@ public class Foo {
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2148,6 +2178,7 @@ E.g. `int[] x = new int[] { 1, 2, 3 };` can be written as `int[] x = { 1, 2, 3 }
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //VariableDeclarator
@@ -2210,6 +2241,7 @@ by the rule {% rule java/codestyle/ControlStatementBraces %}.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//WhileStatement[not(Statement/Block)]</value>
             </property>
diff --git a/pmd-java/src/main/resources/category/java/design.xml b/pmd-java/src/main/resources/category/java/design.xml
index 4a3dfa92dc..04ac51af08 100644
--- a/pmd-java/src/main/resources/category/java/design.xml
+++ b/pmd-java/src/main/resources/category/java/design.xml
@@ -23,6 +23,7 @@ protected constructor in order to prevent instantiation than make the class misl
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -55,6 +56,7 @@ Avoid catching generic exceptions such as NullPointerException, RuntimeException
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -125,6 +127,7 @@ Catch blocks that merely rethrow a caught exception only add to code size and ru
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -161,6 +164,7 @@ code size and runtime complexity.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -230,6 +234,7 @@ public class Foo {
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -262,6 +267,7 @@ Exception, or Error, use a subclassed exception or error instead.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -305,6 +311,7 @@ exceptional cases with a `@throws` Javadoc tag, which allows being more descript
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -335,6 +342,7 @@ is invoked by a inner class.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -367,6 +375,7 @@ Sometimes two consecutive 'if' statements can be consolidated by separating thei
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -532,6 +541,7 @@ Errors are system exceptions. Do not extend them.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -723,6 +733,7 @@ in each object at runtime.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -845,6 +856,7 @@ Use opposite operator instead of negating the whole expression with a logic comp
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1194,6 +1206,7 @@ or
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1248,6 +1261,7 @@ as:
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1293,6 +1307,7 @@ Avoid unnecessary comparisons in boolean expressions, they serve no purpose and
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1353,6 +1368,7 @@ No need to check for null before an instanceof; the instanceof keyword returns f
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1551,6 +1567,7 @@ complexity and find a way to have more fine grained objects.
         <priority>3</priority>
         <properties>
             <property name="maxmethods" type="Integer" description="The method count reporting threshold" min="1" max="1000" value="10"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
                     <!--  FIXME: Refine XPath to discard 'get' and 'set' methods with Block no more than 3 lines,
@@ -1635,6 +1652,7 @@ your API.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-java/src/main/resources/category/java/documentation.xml b/pmd-java/src/main/resources/category/java/documentation.xml
index daee1d547d..8ed06f1481 100644
--- a/pmd-java/src/main/resources/category/java/documentation.xml
+++ b/pmd-java/src/main/resources/category/java/documentation.xml
@@ -91,6 +91,7 @@ and unintentional empty constructors.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -125,6 +126,7 @@ empty methods.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -141,4 +143,4 @@ public void doSomething() {
         </example>
     </rule>
 
-</ruleset>
\ No newline at end of file
+</ruleset>
diff --git a/pmd-java/src/main/resources/category/java/errorprone.xml b/pmd-java/src/main/resources/category/java/errorprone.xml
index 3415522b1e..b7ffed64a2 100644
--- a/pmd-java/src/main/resources/category/java/errorprone.xml
+++ b/pmd-java/src/main/resources/category/java/errorprone.xml
@@ -64,6 +64,7 @@ method visibility, even if they are private. This violates the principle of enca
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -137,6 +138,7 @@ Use of the term 'assert' will conflict with newer versions of Java since it is a
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//VariableDeclaratorId[@Image='assert']</value>
             </property>
@@ -216,6 +218,7 @@ original error, causing other, more subtle problems later on.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -281,6 +284,7 @@ exactly equal to 0.1, as one would expect.  Therefore, it is generally recommend
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -351,6 +355,7 @@ Use of the term 'enum' will conflict with newer versions of Java since it is a r
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//VariableDeclaratorId[@Image='enum']</value>
             </property>
@@ -419,6 +424,7 @@ Each caught exception type should be handled in its own catch clause.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -544,6 +550,7 @@ only add to code size.  Either remove the invocation, or use the return result.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -640,6 +647,7 @@ precision when comparing floating point numbers these are likely to cause logic
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -720,6 +728,7 @@ public String bar(String string) {
         <description>Super should be called at the start of the method</description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -767,6 +776,7 @@ Super should be called at the end of the method
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -846,6 +856,7 @@ in a ClassCastException.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -889,6 +900,7 @@ Object.clone (which is protected) with a public method."
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -961,6 +973,7 @@ Note: This is only possible with Java 1.5 or higher.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1002,6 +1015,7 @@ The method clone() should throw a CloneNotSupportedException.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1181,6 +1195,7 @@ should be annotated with @Test and @Ignore.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //ClassOrInterfaceBodyDeclaration
@@ -1232,6 +1247,7 @@ leaks develop within an application, it should be dealt with JVM options rather
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1287,6 +1303,7 @@ application server should stop the JVM. This rule also checks for the equivalent
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1322,6 +1339,7 @@ Extend Exception or RuntimeException instead of Throwable.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1349,6 +1367,7 @@ Use Environment.getExternalStorageDirectory() instead of "/sdcard"
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//Literal[starts-with(@Image,'"/sdcard')]</value>
             </property>
@@ -1379,6 +1398,7 @@ Note: This is a PMD implementation of the Lint4j rule "A throw in a finally bloc
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//FinallyStatement[descendant::ThrowStatement]</value>
             </property>
@@ -1431,6 +1451,7 @@ performance need (space or time).
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1470,6 +1491,7 @@ or reported.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1509,6 +1531,7 @@ Empty finalize methods serve no purpose and should be removed. Note that Oracle
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1538,6 +1561,7 @@ Empty finally blocks serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1572,6 +1596,7 @@ Empty If Statement finds instances where a condition is checked but nothing is d
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1605,6 +1630,7 @@ Empty initializers serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//Initializer/Block[count(*)=0]</value>
             </property>
@@ -1633,6 +1659,7 @@ Empty block statements serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//BlockStatement/Statement/Block[count(*) = 0]</value>
             </property>
@@ -1666,6 +1693,7 @@ and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1706,6 +1734,7 @@ Empty switch statements serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//SwitchStatement[count(*) = 1]</value>
             </property>
@@ -1734,6 +1763,7 @@ Empty synchronized blocks serve no purpose and should be removed.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//SynchronizedStatement/Block[1][count(*) = 0]</value>
             </property>
@@ -1762,6 +1792,7 @@ Avoid empty try blocks - what's the point?
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1797,6 +1828,7 @@ a while loop that does a lot in the exit expression, rewrite it to make it clear
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1827,6 +1859,7 @@ Tests for null should not use the equals() method. The '==' operator should be u
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1873,6 +1906,7 @@ If the finalize() is implemented, its last action should be to call super.finali
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <!-- in English: a method declaration of finalize(), with no arguments, containing
@@ -1917,6 +1951,7 @@ If the finalize() is implemented, it should do something besides just calling su
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1954,6 +1989,7 @@ Note that Oracle has declared Object.finalize() as deprecated since JDK 9.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -1987,6 +2023,7 @@ Note that Oracle has declared Object.finalize() as deprecated since JDK 9.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2057,6 +2094,7 @@ Avoid instantiating an object just to call getClass() on it; use the .class publ
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2115,6 +2153,7 @@ Avoid jumbled loop incrementers - its usually a mistake, and is confusing even i
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //ForStatement
@@ -2153,6 +2192,7 @@ Some JUnit framework methods are easy to misspell.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2196,6 +2236,7 @@ The suite() method in a JUnit test needs to be both public and static.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2240,6 +2281,7 @@ The rule is replaced by {% rule java/errorprone/ProperLogger %}.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2364,6 +2406,7 @@ may indicate problematic behaviour. Empty cases are ignored as these indicate an
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2417,6 +2460,7 @@ chain needs an own serialVersionUID field. See also [Should an abstract class ha
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2547,6 +2591,7 @@ This legal, but confusing. It is easy to mix up the case labels and the non-case
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//SwitchStatement//BlockStatement/Statement/LabeledStatement</value>
             </property>
@@ -2676,6 +2721,7 @@ Object clone() should be implemented with super.clone().
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2778,6 +2824,7 @@ NullPointerExceptions.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2855,6 +2902,7 @@ formatting is used.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -2945,6 +2993,7 @@ behavior especially when instances are distributed by the container on several J
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3009,6 +3058,7 @@ new StringBuilder("A")   //  1 + 16 = 17
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3049,6 +3099,7 @@ intention to override the equals(Object) method.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3175,6 +3226,7 @@ Do not use "if" statements whose conditionals are always true or always false.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
  <![CDATA[
@@ -3213,6 +3265,7 @@ an error, use the fail() method and provide an indication message of why it did.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3298,6 +3351,7 @@ After checking an object reference for null, you should invoke equals() on that
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3364,6 +3418,7 @@ To make sure the full stacktrace is printed out, use the logging statement with
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3407,6 +3462,7 @@ Use the equals() method instead.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3481,6 +3537,7 @@ class Test {
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -3533,6 +3590,7 @@ Thread.currentThread().getContextClassLoader() instead.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//PrimarySuffix[@Image='getClassLoader']</value>
             </property>
diff --git a/pmd-java/src/main/resources/category/java/multithreading.xml b/pmd-java/src/main/resources/category/java/multithreading.xml
index 35a0d2ec5c..19c73bb7f3 100644
--- a/pmd-java/src/main/resources/category/java/multithreading.xml
+++ b/pmd-java/src/main/resources/category/java/multithreading.xml
@@ -22,6 +22,7 @@ gets it.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//MethodDeclaration[@Synchronized= true()]</value>
             </property>
@@ -65,6 +66,7 @@ it contains methods that are not thread-safe.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -101,6 +103,7 @@ the volatile keyword should not be used for maintenance purpose and portability.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>//FieldDeclaration[@Volatile = true()]</value>
             </property>
@@ -129,6 +132,7 @@ Also EJB's might be moved between machines in a cluster and only managed resourc
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -169,6 +173,7 @@ Explicitly calling Thread.run() method will execute in the caller's thread of co
         </description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -339,6 +344,7 @@ perform efficient map reads without blocking other threads.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -375,6 +381,7 @@ one is chosen.  The thread chosen is arbitrary; thus its usually safer to call n
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-java/src/main/resources/category/java/performance.xml b/pmd-java/src/main/resources/category/java/performance.xml
index 7f1b0e4308..a3feedf2fc 100644
--- a/pmd-java/src/main/resources/category/java/performance.xml
+++ b/pmd-java/src/main/resources/category/java/performance.xml
@@ -21,6 +21,7 @@ It is much better to use one of the type-specific toString() methods instead.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -68,6 +69,7 @@ Instead of manually copying data between two arrays, use the efficient Arrays.co
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -139,6 +141,7 @@ that one covers both.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -212,6 +215,7 @@ adverse impacts on performance.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -297,6 +301,7 @@ Note that new Byte() is deprecated since JDK 9 for that reason.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -470,6 +475,7 @@ Note that new Integer() is deprecated since JDK 9 for that reason.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -503,6 +509,7 @@ Note that new Long() is deprecated since JDK 9 for that reason.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -544,6 +551,7 @@ is faster, but returns only an array of type `Object[]`.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -620,6 +628,7 @@ at the expense of some readability.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -667,6 +676,7 @@ Note that new Short() is deprecated since JDK 9 for that reason.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -735,6 +745,7 @@ if-then statement to increase code readability.
         <priority>3</priority>
         <properties>
             <property name="minimumNumberCaseForASwitch" type="Integer" description="Minimum number of branches for a switch" min="1" max="100" value="3"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -805,6 +816,7 @@ ArrayList is a much better Collection implementation than Vector if thread-safe
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -846,6 +858,7 @@ You must use new ArrayList<>(Arrays.asList(...)) if that is inconvenient for you
 	</description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-java/src/test/resources/net/sourceforge/pmd/ant/classpathtest/ruleset.xml b/pmd-java/src/test/resources/net/sourceforge/pmd/ant/classpathtest/ruleset.xml
index 8b3efddecc..660898adc4 100644
--- a/pmd-java/src/test/resources/net/sourceforge/pmd/ant/classpathtest/ruleset.xml
+++ b/pmd-java/src/test/resources/net/sourceforge/pmd/ant/classpathtest/ruleset.xml
@@ -19,6 +19,7 @@ Avoid jumbled loop incrementers - its usually a mistake, and is confusing even i
      </description>
      <priority>3</priority>
      <properties>
+         <property name="version" value="2.0"/>
          <property name="xpath">
              <value>
  <![CDATA[
diff --git a/pmd-javascript/src/main/resources/category/ecmascript/bestpractices.xml b/pmd-javascript/src/main/resources/category/ecmascript/bestpractices.xml
index a6ce322d0e..5b39319cd2 100644
--- a/pmd-javascript/src/main/resources/category/ecmascript/bestpractices.xml
+++ b/pmd-javascript/src/main/resources/category/ecmascript/bestpractices.xml
@@ -18,6 +18,7 @@ Rules which enforce generally accepted best practices.
         <description>Avoid using with - it's bad news</description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -79,6 +80,7 @@ Global variables can lead to side-effects that are hard to debug.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -116,6 +118,7 @@ is better to explicitly scope the variable name to the nearest enclosing scope w
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -171,6 +174,7 @@ See also: [parseInt()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/R
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-javascript/src/main/resources/category/ecmascript/codestyle.xml b/pmd-javascript/src/main/resources/category/ecmascript/codestyle.xml
index 04d4e1abb2..4b6684db3c 100644
--- a/pmd-javascript/src/main/resources/category/ecmascript/codestyle.xml
+++ b/pmd-javascript/src/main/resources/category/ecmascript/codestyle.xml
@@ -22,6 +22,7 @@ indicative of the bug where the assignment operator '=' was used instead of the
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -72,6 +73,7 @@ Avoid using 'for' statements without using curly braces.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -107,6 +109,7 @@ Avoid using if..else statements without using curly braces.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -146,6 +149,7 @@ Avoid using if statements without using curly braces.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -182,6 +186,7 @@ See also: &lt;http://eslint.org/docs/rules/no-else-return>
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -221,6 +226,7 @@ be misleading.  Considering removing this unnecessary Block.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -256,6 +262,7 @@ if (bar) {
         <description>Unnecessary parentheses should be removed.</description>
         <priority>4</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -285,6 +292,7 @@ will never execute.  This is a bug, or extremely poor style.
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -326,6 +334,7 @@ Avoid using 'while' statements without using curly braces.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-javascript/src/main/resources/category/ecmascript/errorprone.xml b/pmd-javascript/src/main/resources/category/ecmascript/errorprone.xml
index a39190db2e..8a2ffd187f 100644
--- a/pmd-javascript/src/main/resources/category/ecmascript/errorprone.xml
+++ b/pmd-javascript/src/main/resources/category/ecmascript/errorprone.xml
@@ -20,6 +20,7 @@ This rule helps improve code portability due to differences in browser treatment
         </description>
         <priority>1</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -57,6 +58,7 @@ same type. The === operator avoids the casting.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -104,6 +106,7 @@ precision in a floating point number.  This may result in numeric calculations b
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-jsp/src/main/resources/category/jsp/bestpractices.xml b/pmd-jsp/src/main/resources/category/jsp/bestpractices.xml
index 564c645975..b98e02c1a9 100644
--- a/pmd-jsp/src/main/resources/category/jsp/bestpractices.xml
+++ b/pmd-jsp/src/main/resources/category/jsp/bestpractices.xml
@@ -20,6 +20,7 @@ Do not nest JSF component custom actions inside a custom action that iterates ov
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -54,6 +55,7 @@ Do not use an attribute called 'class'. Use "styleclass" for CSS styles.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -84,6 +86,7 @@ little other purpose. Consider switching to JSP comments.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -116,6 +119,7 @@ Do not do a forward from within a JSP file.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-jsp/src/main/resources/category/jsp/design.xml b/pmd-jsp/src/main/resources/category/jsp/design.xml
index 11404c7284..651f827b4d 100644
--- a/pmd-jsp/src/main/resources/category/jsp/design.xml
+++ b/pmd-jsp/src/main/resources/category/jsp/design.xml
@@ -21,6 +21,7 @@ Externalized script could be reused between pages.  Browsers can also cache the
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -59,6 +60,7 @@ Scripts should be part of Tag Libraries, rather than part of JSP pages.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -105,6 +107,7 @@ Scriptlets should be factored into Tag Libraries or JSP declarations, rather tha
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-jsp/src/main/resources/category/jsp/errorprone.xml b/pmd-jsp/src/main/resources/category/jsp/errorprone.xml
index 1006fb141d..2f0ea86a7d 100644
--- a/pmd-jsp/src/main/resources/category/jsp/errorprone.xml
+++ b/pmd-jsp/src/main/resources/category/jsp/errorprone.xml
@@ -20,6 +20,7 @@ A missing 'meta' tag or page directive will trigger this rule, as well as a non-
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-jsp/src/main/resources/category/jsp/security.xml b/pmd-jsp/src/main/resources/category/jsp/security.xml
index 57ebba02ea..fd2125bfc8 100644
--- a/pmd-jsp/src/main/resources/category/jsp/security.xml
+++ b/pmd-jsp/src/main/resources/category/jsp/security.xml
@@ -21,6 +21,7 @@ through SSL. See http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q261188
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-plsql/src/main/resources/category/plsql/bestpractices.xml b/pmd-plsql/src/main/resources/category/plsql/bestpractices.xml
index d18992823f..54e026cb9a 100644
--- a/pmd-plsql/src/main/resources/category/plsql/bestpractices.xml
+++ b/pmd-plsql/src/main/resources/category/plsql/bestpractices.xml
@@ -21,6 +21,7 @@ Rules which enforce generally accepted best practices.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-plsql/src/main/resources/category/plsql/codestyle.xml b/pmd-plsql/src/main/resources/category/plsql/codestyle.xml
index 2e01fea8c7..c5e9e1d453 100644
--- a/pmd-plsql/src/main/resources/category/plsql/codestyle.xml
+++ b/pmd-plsql/src/main/resources/category/plsql/codestyle.xml
@@ -105,6 +105,7 @@ https://docs.oracle.com/cd/B28359_01/appdev.111/b28370/static.htm#BABIIHBJ
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -146,6 +147,7 @@ In case you have loops please name the loop variables more meaningful.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-plsql/src/main/resources/category/plsql/design.xml b/pmd-plsql/src/main/resources/category/plsql/design.xml
index 1c5cf2b278..7322ca2cd3 100644
--- a/pmd-plsql/src/main/resources/category/plsql/design.xml
+++ b/pmd-plsql/src/main/resources/category/plsql/design.xml
@@ -499,6 +499,7 @@ have more fine grained objects.
         <priority>3</priority>
         <properties>
             <property name="maxmethods" type="Integer" description="The method count reporting threshold" min="1" max="1000" value="1"/>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-plsql/src/main/resources/category/plsql/errorprone.xml b/pmd-plsql/src/main/resources/category/plsql/errorprone.xml
index ff7127701b..198bfb6edb 100644
--- a/pmd-plsql/src/main/resources/category/plsql/errorprone.xml
+++ b/pmd-plsql/src/main/resources/category/plsql/errorprone.xml
@@ -20,6 +20,7 @@ TO_DATE(TO_CHAR(date-variable)) used to remove time component - use TRUNC(date-v
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -60,6 +61,7 @@ TO_DATE without date format- use TO_DATE(expression, date-format)
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -112,6 +114,7 @@ TO_TIMESTAMP without date format- use TO_TIMESTAMP(expression, date-format)
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-test/src/main/resources/rulesets/dummy/basic.xml b/pmd-test/src/main/resources/rulesets/dummy/basic.xml
index db1bd0c98a..ba7589bf21 100644
--- a/pmd-test/src/main/resources/rulesets/dummy/basic.xml
+++ b/pmd-test/src/main/resources/rulesets/dummy/basic.xml
@@ -26,6 +26,7 @@ Just for test
         <priority>3</priority>
         <example> </example>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value><![CDATA[
 //DummyNode
@@ -33,4 +34,4 @@ Just for test
             </property>
         </properties>
     </rule>"
-</ruleset>
\ No newline at end of file
+</ruleset>
diff --git a/pmd-vm/src/main/resources/category/vm/design.xml b/pmd-vm/src/main/resources/category/vm/design.xml
index 7bea5920f7..d5d65f4f20 100644
--- a/pmd-vm/src/main/resources/category/vm/design.xml
+++ b/pmd-vm/src/main/resources/category/vm/design.xml
@@ -67,6 +67,7 @@ Avoid inline styles. Use css classes instead.
         </description>
         <priority>2</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-xml/src/main/resources/category/pom/errorprone.xml b/pmd-xml/src/main/resources/category/pom/errorprone.xml
index d459a47a8c..e3143511ca 100644
--- a/pmd-xml/src/main/resources/category/pom/errorprone.xml
+++ b/pmd-xml/src/main/resources/category/pom/errorprone.xml
@@ -23,6 +23,7 @@ The following types are considered valid: pom, jar, maven-plugin, ejb, war, ear,
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
@@ -70,6 +71,7 @@ By far the most common problem is the use of &#x24;{project.version} in a BOM or
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-xml/src/main/resources/category/xml/errorprone.xml b/pmd-xml/src/main/resources/category/xml/errorprone.xml
index 46f598d8e4..48f7cceea2 100644
--- a/pmd-xml/src/main/resources/category/xml/errorprone.xml
+++ b/pmd-xml/src/main/resources/category/xml/errorprone.xml
@@ -20,6 +20,7 @@ An XML CDATA section begins with a &lt;![CDATA[ marker, which has only one [, an
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
                 <value>
 <![CDATA[
diff --git a/pmd-xml/src/main/resources/category/xsl/codestyle.xml b/pmd-xml/src/main/resources/category/xsl/codestyle.xml
index fd87bfc1ff..16e1b0ff46 100644
--- a/pmd-xml/src/main/resources/category/xsl/codestyle.xml
+++ b/pmd-xml/src/main/resources/category/xsl/codestyle.xml
@@ -21,6 +21,7 @@ The XPath concat() functions accepts as many arguments as required so you can ha
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
 <!-- the use of node() allow to target any node with an select attribute
      but also workaround the ambiguity of having the xsl namespace in the
diff --git a/pmd-xml/src/main/resources/category/xsl/performance.xml b/pmd-xml/src/main/resources/category/xsl/performance.xml
index c23f1a8642..bd6218db61 100644
--- a/pmd-xml/src/main/resources/category/xsl/performance.xml
+++ b/pmd-xml/src/main/resources/category/xsl/performance.xml
@@ -23,6 +23,7 @@ cutting through 100% of the document.
         </description>
         <priority>3</priority>
         <properties>
+            <property name="version" value="2.0"/>
             <property name="xpath">
 <!-- the use of node() allow to target any node with an select attribute
      but also workaround the ambiguity of having the xsl namespace in the