diff --git a/checkstyle-sonar-plugin/config/pmd-main.xml b/checkstyle-sonar-plugin/config/pmd-main.xml
new file mode 100644
index 00000000..9eb2deb3
--- /dev/null
+++ b/checkstyle-sonar-plugin/config/pmd-main.xml
@@ -0,0 +1,20 @@
+<?xml version="1.0"?>
+<ruleset name="PMD ruleset for Checkstyle"
+         xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0
+                             http://pmd.sourceforge.net/ruleset_2_0_0.xsd">
+    <description>
+        PMD ruleset for Checkstyle main code (copy from main repo)
+    </description>
+    <exclude-pattern>.*/src/test/.*</exclude-pattern>
+    <rule ref="checkstyle-sonar-plugin/config/pmd.xml">
+      <!-- until https://github.com/checkstyle/sonar-checkstyle/issues/161 -->
+      <exclude name="CommentRequired"/>
+      <exclude name="AvoidCatchingGenericException"/>
+      <exclude name="AvoidFileStream"/>
+      <exclude name="ClassNamingConventions"/>
+      <exclude name="TooManyMethods"/>
+    </rule>
+
+</ruleset>
diff --git a/checkstyle-sonar-plugin/config/pmd-test.xml b/checkstyle-sonar-plugin/config/pmd-test.xml
new file mode 100644
index 00000000..d57077ce
--- /dev/null
+++ b/checkstyle-sonar-plugin/config/pmd-test.xml
@@ -0,0 +1,73 @@
+<?xml version="1.0"?>
+<ruleset name="PMD ruleset for Checkstyle"
+         xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0
+                             http://pmd.sourceforge.net/ruleset_2_0_0.xsd">
+    <description>
+        PMD ruleset for Checkstyle tests (copy from main repo)
+    </description>
+    <exclude-pattern>.*/src/main/.*</exclude-pattern>
+
+    <rule ref="checkstyle-sonar-plugin/config/pmd.xml">
+        <!--We do throws Exception, as any exception that in not caught in test should fail
+            a test that is expected behavior and we like it as it follow fail-fast and helps
+            to avoid extra catch blocks-->
+        <exclude name="SignatureDeclareThrowsException"/>
+        <!--it madness to move all string values to common variables,
+            it will be hard to read test code-->
+        <exclude name="AvoidDuplicateLiterals"/>
+        <!--we do not need javadoc on test code-->
+        <exclude name="CommentRequired"/>
+        <!--we like static imports in UTs as them minimize the code and we know that most of
+            such methods are from UT+moks frameworks-->
+        <exclude name="TooManyStaticImports"/>
+        <!--we try to keep all testing for class in one place/class/file to ease navigation
+            between target class and it's test-->
+        <exclude name="TooManyMethods"/>
+        <!--we have too much UTs for each main class, it is better to keep all tests in one
+            file to ease navigation and search for tes-->
+        <exclude name="CouplingBetweenObjects"/>
+        <!--we have too much UTs for each main class, it is better to keep all tests in one
+            file to ease navigation and search for test-->
+        <exclude name="ExcessiveImports"/>
+        <!--checkstyle do not use IP in configuration, so all values in tests are ok to use,
+            they just another test string data-->
+        <exclude name="AvoidUsingHardCodedIP"/>
+        <!--UTests are required to be public by design-->
+        <exclude name="ExcessivePublicCount"/>
+        <!--we have too much UTs for each main class, it is better to keep all tests in one
+            file to ease navigation and search for test-->
+        <exclude name="ExcessiveClassLength"/>
+        <!--we want to avoid wide throws signature, it is just test-->
+        <exclude name="AvoidCatchingGenericException"/>
+        <!--we do not want invest extra time to make logic ideal in test method, may be later...-->
+        <exclude name="NPathComplexity"/>
+        <!--conflicts with checkstyle rule-->
+        <exclude name="JUnitUseExpected"/>
+        <!--will be addressed in https://github.com/checkstyle/checkstyle/projects/5-->
+        <exclude name="NonThreadSafeSingleton"/>
+        <!-- too much false positives -->
+        <exclude name="JUnitAssertionsShouldIncludeMessage"/>
+        <!-- verify from another library is used -->
+        <exclude name="JUnitTestsShouldIncludeAssert"/>
+        <!-- until https://github.com/checkstyle/sonar-checkstyle/issues/161 -->
+        <exclude name="AvoidFileStream"/>
+    </rule>
+
+    <rule ref="category/java/design.xml/NcssCount">
+        <properties>
+            <!-- We want to keep it all in one place. -->
+            <property name="classReportLevel" value="1000"/>
+            <!-- A big enough value to satisfy the most cases. -->
+            <property name="methodReportLevel" value="100"/>
+        </properties>
+    </rule>
+
+    <rule ref="category/java/bestpractices.xml/JUnitTestContainsTooManyAsserts">
+        <properties>
+            <property name="maximumAsserts" value="15"/>
+        </properties>
+    </rule>
+
+</ruleset>
diff --git a/checkstyle-sonar-plugin/config/pmd.xml b/checkstyle-sonar-plugin/config/pmd.xml
index c3896510..558dbcf0 100644
--- a/checkstyle-sonar-plugin/config/pmd.xml
+++ b/checkstyle-sonar-plugin/config/pmd.xml
@@ -3,248 +3,158 @@
         xmlns="http://pmd.sourceforge.net/ruleset/2.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0
-         http://pmd.sourceforge.net/ruleset_2_0_0.xsd">
+                            http://pmd.sourceforge.net/ruleset_2_0_0.xsd">
   <description>
-    PMD ruleset for Checkstyle (copy from main repo)
+    PMD common ruleset for Checkstyle main/test sourcesets (copy from main repo)
   </description>
-  <rule ref="rulesets/java/basic.xml"/>
-  <rule ref="rulesets/java/braces.xml"/>
-  <rule ref="rulesets/java/clone.xml"/>
-  <rule ref="rulesets/java/codesize.xml">
-    <!-- we are using CyclomaticComplexity -->
-    <exclude name="ModifiedCyclomaticComplexity"/>
-    <!-- we are using CyclomaticComplexity -->
-    <exclude name="StdCyclomaticComplexity"/>
-  </rule>
 
-  <rule ref="rulesets/java/codesize.xml/CyclomaticComplexity">
-    <properties>
-      <property name="showClassesComplexity" value="false"/>
-      <property name="reportLevel" value="11"/>
-      <!-- very big logic in test -->
-      <property name="violationSuppressXPath" value="//MethodDeclaration[@Name='validateSonarProperties' and ../../..[@Image='ChecksTest']]"/>
-    </properties>gnature
-  </rule>
-  <rule ref="rulesets/java/codesize.xml/NPathComplexity">
-    <properties>
-      <!-- very big logic in test -->
-      <property name="violationSuppressXPath" value="//MethodDeclaration[@Name='validateSonarProperties' and ../../..[@Image='ChecksTest']]"/>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/codesize.xml/TooManyFields">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/codesize.xml/TooManyMethods">
-    <properties>
-      <property name="maxmethods" value="20"/>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/codesize.xml/ExcessiveClassLength">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/codesize.xml/ExcessiveMethodLength">
-    <properties>
-    </properties>
+  <rule ref="category/java/bestpractices.xml">
+    <!-- We do not care about this minor overhead, we are not Android application and we do not
+         want to change visibility of methods. Package-private visibility should be avoid almost
+         always. -->
+    <exclude name="AccessorMethodGeneration"/>
+    <!-- The PMD mistakes the AbstractViolationReporter::log() as a debug log. -->
+    <exclude name="GuardLogStatement"/>
+    <!-- Till https://github.com/pmd/pmd/issues/1181 -->
+    <exclude name="UnusedPrivateMethod"/>
   </rule>
 
-  <rule ref="rulesets/java/comments.xml">
-    <!-- activate after chekcstyle is activated -->
-    <exclude name="CommentRequired"/>
-    <!-- we use class comments as source for xdoc files, so content is big and that is by design -->
+  <rule ref="category/java/documentation.xml">
+    <!-- We use class comments as source for xdoc files,
+         so content is big and that is by design. -->
     <exclude name="CommentSize"/>
   </rule>
 
-  <rule ref="rulesets/java/controversial.xml">
-    <!-- calling super() is completely pointless, no matter if class inherits anything or not; it is meaningful only if you do not call implicit constructor of base class -->
-    <exclude name="CallSuperInConstructor"/>
-    <!-- We reuse Check instances between java files, we need to clear state of class in beginTree() methods -->
-    <exclude name="NullAssignment"/>
-    <!-- it is possible only in functional languages and fanatically-pristine code, without additional option that are done at ReturnCountExtendedCheck it is not good rule -->
-    <exclude name="OnlyOneReturn"/>
-    <!-- opposite to UnnecessaryConstructor -->
+  <rule ref="category/java/codestyle.xml">
+    <!-- Opposite to UnnecessaryConstructor. -->
     <exclude name="AtLeastOneConstructor"/>
-    <!-- that rule is too buggy, too much false positives-->
-    <exclude name="DataflowAnomalyAnalysis"/>
-    <!-- turning local variables to fields create design problems and extend scope of variable -->
+    <!-- Turning a local variable to the field may create design problems and extend the scope of
+           the variable. -->
     <exclude name="AvoidFinalLocalVariable"/>
-    <!-- conflicts with names that does not mean in/out -->
+    <!-- Conflicts with names that does not mean in/out. -->
     <exclude name="AvoidPrefixingMethodParameters"/>
-    <!-- that is not practical, no options to allow some magic numbers, we will use our implementation -->
-    <exclude name="AvoidLiteralsInIfCondition"/>
-    <!-- Checkstyle is not thread safe -->
-    <exclude name="UseConcurrentHashMap"/>
-  </rule>
-  <rule ref="rulesets/java/controversial.xml/AvoidUsingShortType">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/coupling.xml">
-    <!-- produce too much violations, suppressed till we figure out how useful that metrics-->
-    <exclude name="LawOfDemeter"/>
-    <!-- this rule is for managing import, we have special Check for that -->
-    <exclude name="LoosePackageCoupling"/>
-  </rule>
-  <rule ref="rulesets/java/coupling.xml/ExcessiveImports">
-    <properties>
-      <!-- ChecksTest integrates alot of classes from Checkstyle to build complete documentation -->
-      <property name="violationSuppressXPath" value="//ClassOrInterfaceDeclaration[@Image='ChecksTest']"/>
-    </properties>
+    <!-- Calling super() is completely pointless, no matter if class inherits anything or not;
+         it is meaningful only if you do not call implicit constructor of the base class. -->
+    <exclude name="CallSuperInConstructor"/>
+    <!-- Till https://github.com/checkstyle/checkstyle/issues/5665 -->
+    <exclude name="CommentDefaultAccessModifier"/>
+    <!-- Pollutes code with modifiers. -->
+    <exclude name="LocalVariableCouldBeFinal"/>
+    <!-- Pollutes the code with modifiers. We use the ParameterAssignmentCheck to protect the
+         parameters. -->
+    <exclude name="MethodArgumentCouldBeFinal"/>
+    <!-- It is possible only in functional languages and fanatically-pristine code, without
+         additional option that are done at ReturnCountExtendedCheck it is not a good rule. -->
+    <exclude name="OnlyOneReturn"/>
+    <!-- We use CheckstyleCustomShortVariable, to control the length and skip Override methods. -->
+    <exclude name="ShortVariable"/>
   </rule>
-  <rule ref="rulesets/java/coupling.xml/CouplingBetweenObjects">
+  <rule ref="category/java/codestyle.xml/LongVariable">
     <properties>
+      <!-- Nothing bad with the long and descriptive variable names if only they fit the line,
+           but still keep it reasonable. -->
+      <property name="minimum" value="45"/>
     </properties>
   </rule>
-
-  <rule ref="rulesets/java/design.xml">
-    <!-- extra final modifier does not make code more secure in that cases-->
-    <exclude name="ImmutableField"/>
-    <!-- this rule does not have any option, unreasonable to use -->
-    <exclude name="MissingBreakInSwitch"/>
-    <!-- we need compare by ref as Tree structure is immutable, we can easily rely on refs -->
+  <rule ref="category/java/errorprone.xml">
+    <!-- That rule is not practical, no options to allow some magic numbers,
+         we will use our implementation. -->
+    <exclude name="AvoidLiteralsInIfCondition"/>
+    <!-- It is not our goal for now to keep all Serializable, maybe in the future. -->
+    <exclude name="BeanMembersShouldSerialize"/>
+    <!-- We need compare by ref as Tree structure is immutable, we can easily
+         rely on refs. -->
     <exclude name="CompareObjectsWithEquals"/>
-    <!-- we will use our own declaration order logic -->
-    <exclude name="FieldDeclarationsShouldBeAtStartOfClass"/>
-    <!-- too much alarms of Checks, we will never move logic out of Check, each Check is independent logic container -->
-    <exclude name="GodClass"/>
-    <!-- need to be be investigated -->
-    <exclude name="SingularField"/>
-  </rule>
-<!--
-  <rule ref="rulesets/java/design.xml/SingularField">
-    <properties>
-      <property name="violationSuppressXPath" value="//ClassOrInterfaceDeclaration[@Image='CheckstyleVersion']"/>
-    </properties>
-  </rule>
--->
-  <rule ref="rulesets/java/design.xml/AccessorClassGeneration">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/design.xml/PreserveStackTrace">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/design.xml/EmptyMethodInAbstractClassShouldBeAbstract">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/design.xml/AbstractClassWithoutAnyMethod">
-    <properties>
-    </properties>
+    <!-- Too many false positives. -->
+    <exclude name="DataflowAnomalyAnalysis"/>
+    <!-- This rule does not have any option, unreasonable to use. -->
+    <exclude name="MissingBreakInSwitch"/>
+    <!-- We reuse Check instances between java files, we need to clear state of
+         class in beginTree() methods. -->
+    <exclude name="NullAssignment"/>
+    <!-- Till https://github.com/checkstyle/checkstyle/issues/5680 -->
+    <exclude name="UseProperClassLoader"/>
   </rule>
-
-  <rule ref="rulesets/java/design.xml/AvoidDeeplyNestedIfStmts">
+  <rule ref="category/java/errorprone.xml/AvoidDuplicateLiterals">
     <properties>
-      <!-- default is 3 but we try to use single point of exit from method and that require extra IFs -->
-      <property name="problemDepth" value="4"/>
+      <!-- Annotations like '@SuppressWarnings' don't need to be checked, it is better to keep their
+             strings connected to the annotation instead of separating. -->
+      <property name="skipAnnotations" value="true"/>
     </properties>
   </rule>
-
-  <rule ref="rulesets/java/empty.xml"/>
-  <rule ref="rulesets/java/empty.xml/EmptyCatchBlock">
+  <rule ref="category/java/errorprone.xml/EmptyCatchBlock">
     <properties>
       <property name="allowCommentedBlocks" value="true"/>
     </properties>
   </rule>
 
-  <rule ref="rulesets/java/finalizers.xml"/>
-  <rule ref="rulesets/java/imports.xml"/>
-  <rule ref="rulesets/java/imports.xml/TooManyStaticImports">
-    <properties>
-      <property name="maximumStaticImports" value="10" />
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/javabeans.xml">
-    <!-- too many false-positives -->
-    <exclude name="BeanMembersShouldSerialize"/>
-  </rule>
-
-  <rule ref="rulesets/java/junit.xml">
-    <!-- verify from another library is used -->
-    <exclude name="JUnitTestsShouldIncludeAssert" />
-    <!-- too much false positives -->
-    <exclude name="JUnitAssertionsShouldIncludeMessage"/>
-  </rule>
-  <rule ref="rulesets/java/junit.xml/JUnitTestContainsTooManyAsserts">
-    <properties>
-      <property name="maximumAsserts" value="15" />
-    </properties>
-  </rule>
-
-  <rule ref="rulesets/java/logging-jakarta-commons.xml">
-    <!-- slf4j does not need guards -->
-    <exclude name="GuardLogStatement"/>
-  </rule>
-  <rule ref="rulesets/java/logging-java.xml">
-    <!-- NPE -->
-    <exclude name="InvalidSlf4jMessageFormat"/>
+  <rule ref="category/java/design.xml">
+    <!-- Too much false-positives on the check classes.
+         We do not follow the philosophy of complete encapsulation, we like data classes
+         (preferable immutable) to transfer content from one part to another.
+         There is no way to configure the rule (it has no properties). -->
+    <exclude name="DataClass"/>
+    <!-- Too much alarms on the check classes, we will never move logic out of the check,
+         each check is an independent logic container. -->
+    <exclude name="GodClass"/>
+    <!-- Too many violations, will be suppressed until we find out how use these metrics. -->
+    <exclude name="LawOfDemeter"/>
+    <!-- We use our ImportControl to control imports in packages and classes. -->
+    <exclude name="LoosePackageCoupling"/>
   </rule>
-  <rule ref="rulesets/java/logging-java.xml/SystemPrintln">
+  <rule ref="category/java/design.xml/NcssCount">
     <properties>
+      <property name="methodReportLevel" value="32"/>
     </properties>
   </rule>
-  <rule ref="rulesets/java/logging-java.xml/AvoidPrintStackTrace">
+  <rule ref="category/java/design.xml/CyclomaticComplexity">
     <properties>
+      <property name="classReportLevel" value="76"/>
+      <property name="methodReportLevel" value="11"/>
+      <!-- ChecksTest is needed until all suppressions are removed. -->
+      <property name="violationSuppressXPath"
+          value="//ClassOrInterfaceDeclaration[@Image='ChecksTest']//MethodDeclaration[@Name='validateSonarProperties']
+    | //ClassOrInterfaceDeclaration[@Image='ChecksTest']//MethodDeclaration[@Name='getFinalProperties']"/>
     </properties>
   </rule>
 
-  <rule ref="rulesets/java/migrating.xml"/>
-
-  <rule ref="rulesets/java/naming.xml">
-    <!-- we use CheckstyleCustomShortVariable, to control lenght (will be fixed in PMD 5.4) and skip Override methods -->
-    <exclude name="ShortVariable"/>
-  </rule>
-  <rule ref="rulesets/java/naming.xml/AbstractNaming">
-    <properties>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/naming.xml/LongVariable">
-    <properties>
-      <!-- nothing bad in long and descriptive variable names if only they fit line, but still keep it reasonable -->
-      <property name="minimum" value="45"/>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/naming.xml/ShortClassName">
-    <properties>
-    </properties>
+  <rule ref="category/java/multithreading.xml">
+    <!-- Checkstyle is not thread safe till https://github.com/checkstyle/checkstyle/projects/5. -->
+    <exclude name="UseConcurrentHashMap"/>
   </rule>
 
-  <rule ref="rulesets/java/optimizations.xml">
-    <!--produces more false-positives than real problems-->
+  <rule ref="category/java/performance.xml">
+    <!-- Produces more false positives than real problems. -->
     <exclude name="AvoidInstantiatingObjectsInLoops"/>
-    <!--pollutes code with modifiers-->
-    <exclude name="LocalVariableCouldBeFinal"/>
-    <!--pollutes code with modifiers-->
-    <exclude name="MethodArgumentCouldBeFinal"/>
-    <!--not configurable, decreases readability-->
+    <!-- Not configurable, decreases readability. -->
     <exclude name="UseStringBufferForStringAppends"/>
   </rule>
-  <rule ref="rulesets/java/strictexception.xml/AvoidCatchingGenericException">
-    <properties>
-      <!-- need to be be investigated -->
-      <!-- CheckstyleSeverityUtils is ok to catch all in util methods-->
-      <property name="violationSuppressXPath" value="//ClassOrInterfaceDeclaration[@Image='CheckstyleAuditListener' or @Image='CheckstyleExecutor'] or //MethodDeclaration[@Name='fromSeverity' and ../../..[@Image='CheckstyleSeverityUtils']]"/>
-    </properties>
-  </rule>
-  <rule ref="rulesets/java/strictexception.xml/SignatureDeclareThrowsException">
-    <properties>
-      <!-- not sure if this is good or bad -->
-      <property name="violationSuppressXPath" value="//MethodDeclaration[@Name='verifyTestConfigurationFiles' and ../../..[@Image='ChecksTest']] or //MethodDeclaration[@Name='getCheckstyleConfiguration' and ../../..[@Image='CheckstyleConfigurationTest']] or //MethodDeclaration[@Name='canGenerateXmlReportInEnglish' and ../../..[@Image='CheckstyleExecutorTest']]"/>
-    </properties>
-  </rule>
 
-  <rule ref="rulesets/java/strings.xml">
-    <!-- too much false positived in tests -->
-    <exclude name="AvoidDuplicateLiterals" />
-  </rule>
-  <rule ref="rulesets/java/sunsecure.xml/MethodReturnsInternalArray">
-    <properties>
+  <!-- Checkstyle own rules. -->
+  <rule name="CheckstyleCustomShortVariable"
+        message="Avoid variables with short names that shorter than 2 symbols: {0}"
+        language="java"
+        class="net.sourceforge.pmd.lang.rule.XPathRule"
+        externalInfoUrl="">
+    <description>
+      Fields, local variables, or parameter names that are very short are not helpful to the reader.
+    </description>
+    <priority>3</priority>
+    <properties>
+      <property name="xpath">
+        <value>
+          <![CDATA[
+          //VariableDeclaratorId[string-length(@Image) < 2]
+          [not(ancestor::ForInit)]
+          [not(../../VariableDeclarator and ../../../LocalVariableDeclaration
+                and ../../../../ForStatement)]
+          [not((ancestor::FormalParameter) and (ancestor::TryStatement))]
+          [not(ancestor::ClassOrInterfaceDeclaration[
+              //MarkerAnnotation/Name[pmd-java:typeIs('java.lang.Override')]])]
+          ]]>
+        </value>
+      </property>
     </properties>
   </rule>
-  <rule ref="rulesets/java/typeresolution.xml"/>
-  <rule ref="rulesets/java/unnecessary.xml"/>
-  <rule ref="rulesets/java/unusedcode.xml"/>
 
 </ruleset>
diff --git a/checkstyle-sonar-plugin/pom.xml b/checkstyle-sonar-plugin/pom.xml
index 7ff39ebc..f957baa4 100644
--- a/checkstyle-sonar-plugin/pom.xml
+++ b/checkstyle-sonar-plugin/pom.xml
@@ -217,17 +217,18 @@
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-pmd-plugin</artifactId>
-        <version>3.7</version>
+        <version>3.10.0</version>
         <configuration>
+          <analysisCache>false</analysisCache>
           <targetJdk>${java.version}</targetJdk>
           <minimumTokens>20</minimumTokens>
           <skipEmptyReport>false</skipEmptyReport>
           <failOnViolation>true</failOnViolation>
           <printFailingErrors>true</printFailingErrors>
-          <linkXRef>false</linkXRef>
           <includeTests>true</includeTests>
           <rulesets>
-            <ruleset>config/pmd.xml</ruleset>
+            <ruleset>config/pmd-main.xml</ruleset>
+            <ruleset>config/pmd-test.xml</ruleset>
           </rulesets>
         </configuration>
         <executions>
@@ -237,6 +238,28 @@
             </goals>
           </execution>
         </executions>
+        <dependencies>
+          <dependency>
+            <groupId>net.sourceforge.pmd</groupId>
+            <artifactId>pmd-java</artifactId>
+            <version>6.6.0</version>
+          </dependency>
+          <dependency>
+            <groupId>net.sourceforge.pmd</groupId>
+            <artifactId>pmd-core</artifactId>
+            <version>6.6.0</version>
+          </dependency>
+          <dependency>
+            <groupId>net.sourceforge.pmd</groupId>
+            <artifactId>pmd-javascript</artifactId>
+            <version>6.6.0</version>
+          </dependency>
+          <dependency>
+            <groupId>net.sourceforge.pmd</groupId>
+            <artifactId>pmd-jsp</artifactId>
+            <version>6.6.0</version>
+          </dependency>
+        </dependencies>
       </plugin>
       <plugin>
         <groupId>org.codehaus.mojo</groupId>