This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-pmd-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new f062d9d  Refresh the plugin site and README
f062d9d is described below

commit f062d9d75dea5c491a22dfc0324a9d4c97b8cb2d
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Wed Nov 18 00:04:09 2026 +0000

    Refresh the plugin site and README
---
 README.md                                          | 89 ++++++++--------------
 src/site/markdown/examples/cpdCsharp.md.vm         |  2 +-
 src/site/markdown/examples/javascriptReport.md.vm  |  4 +-
 src/site/markdown/examples/jspReport.md.vm         |  4 +-
 .../markdown/examples/multi-module-config.md.vm    |  6 +-
 src/site/markdown/examples/targetJdk.md.vm         |  6 +-
 .../examples/upgrading-PMD-at-runtime.md.vm        | 20 ++---
 src/site/markdown/examples/usingRuleSets.md.vm     | 22 +++---
 src/site/markdown/faq.md                           | 13 +++-
 src/site/markdown/index.md.vm                      | 36 ++++++---
 src/site/markdown/usage.md.vm                      | 11 ++-
 11 files changed, 100 insertions(+), 113 deletions(-)

diff --git a/README.md b/README.md
index 0272e7f..2a4fbbb 100644
--- a/README.md
+++ b/README.md
@@ -14,71 +14,46 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 -->
-Contributing to [Apache Maven PMD 
Plugin](https://maven.apache.org/plugins/maven-pmd-plugin/)
-======================
 
-[![Apache License, Version 2.0, January 
2004](https://img.shields.io/github/license/apache/maven.svg?label=License)][license]
-[![Maven 
Central](https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-pmd-plugin.svg?label=Maven%20Central)](https://search.maven.org/artifact/org.apache.maven.plugins/maven-pmd-plugin)
+# Apache Maven PMD Plugin
+
+[![Apache License, Version 2.0, January 
2004](https://img.shields.io/github/license/apache/maven.svg?label=License)](https://www.apache.org/licenses/LICENSE-2.0)
+[![Maven 
Central](https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-pmd-plugin.svg?label=Maven%20Central)](https://central.sonatype.com/artifact/org.apache.maven.plugins/maven-pmd-plugin)
 [![Reproducible 
Builds](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/jvm-repo-rebuild/reproducible-central/master/content/org/apache/maven/plugins/maven-pmd-plugin/badge.json)](https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/plugins/maven-pmd-plugin/README.md)
-[![GitHub 
CI](https://github.com/apache/maven-pmd-plugin/actions/workflows/maven-verify.yml/badge.svg)](https://github.com/apache/maven-pmd-plugin/actions/workflows/maven-verify.yml)
-[![Jenkins 
Status](https://img.shields.io/jenkins/s/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master.svg?)][build]
-[![Jenkins 
tests](https://img.shields.io/jenkins/t/https/ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master.svg?)][test-results]
+[![Verify](https://github.com/apache/maven-pmd-plugin/actions/workflows/maven-verify.yml/badge.svg)](https://github.com/apache/maven-pmd-plugin/actions/workflows/maven-verify.yml)
+
+Runs the [PMD](https://pmd.github.io/) static code analyzer and its Copy/Paste 
Detector (CPD) in a Maven build.
+The `check` and `cpd-check` goals fail the build on rule violations or 
duplicated code; the `pmd` and `cpd`
+goals, and their `aggregate-*` variants for multi-module builds, publish the 
results as site reports.
+
+The plugin needs Maven 3.9.0 or later on Java 8 or later. Each release ships 
with a default PMD version, which
+you can [override at 
runtime](https://maven.apache.org/plugins/maven-pmd-plugin/examples/upgrading-PMD-at-runtime.html).
 
-You have found a bug, or you have an idea for a cool new feature? Contributing
-code is a great way to give something back to the open source community. Before
-you dig right into the code, there are a few guidelines that we need
-contributors to follow so that we can have a chance of keeping on top of
-things.
+- Documentation: <https://maven.apache.org/plugins/maven-pmd-plugin/>
+- Issues: <https://github.com/apache/maven-pmd-plugin/issues>
+- Release notes: <https://github.com/apache/maven-pmd-plugin/releases>
 
-Getting Started
----------------
+## Build
 
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature, it makes sense to discuss 
your changes 
-  on the [dev list][ml-list] first. 
-  This way you can make sure you're not wasting your time on something that 
isn't 
-  considered to be in Apache Maven's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
-  + Clearly describe the issue, including steps to reproduce when it is a bug.
-  + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
+```shell
+mvn verify
+```
 
-Making and Submitting Changes
---------------
+The integration tests under `src/it` run with the `run-its` profile:
 
-We accept Pull Requests via GitHub. The [developer mailing list][ml-list] is 
the
-main channel of communication for contributors.  
-There are some guidelines which will make applying PRs easier for us:
-+ Create a topic branch from where you want to base your work (this is usually 
the master branch).
-  Push your changes to a topic branch in your fork of the repository.
-+ Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
-  patches should only highlight the actual difference, not being disturbed by 
any formatting issues:
-  + Only use spaces for indentation.
-  + Create minimal diffs - disable on save actions like reformat source code 
or organize imports. 
-    If you feel the source code should be reformatted, create a separate PR 
for this change.
-  + Check for unnecessary whitespace with `git diff --check` before committing.
-+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was 
accidentally broken.
-+ Submit a pull request to the repository in the Apache organization.
+```shell
+mvn -Prun-its verify
+```
 
-If you plan to contribute on a regular basis, please consider filing a 
[contributor license agreement][cla].
+To build the plugin site locally, including the goal pages:
 
-Additional Resources
---------------------
+```shell
+mvn -Preporting site
+```
 
-+ [Contributing 
patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
-+ [Contributor License Agreement][cla]
-+ [General GitHub documentation](https://help.github.com/)
-+ [GitHub pull request 
documentation](https://help.github.com/send-pull-requests/)
-+ [Apache Maven X Account](https://x.com/ASFMavenProject)
-+ [Apache Maven Bluesky Account](https://bsky.app/profile/maven.apache.org)
-+ [Apache Maven Mastodon 
Account](https://mastodon.social/deck/@[email protected])
+## Contributing
 
-[license]: https://www.apache.org/licenses/LICENSE-2.0
-[ml-list]: https://maven.apache.org/mailing-lists.html
-[code-style]: https://maven.apache.org/developers/conventions/code.html
-[cla]: https://www.apache.org/licenses/#clas
-[maven-wiki]: https://cwiki.apache.org/confluence/display/MAVEN/Index
-[test-results]: 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/lastCompletedBuild/testReport/
-[build]: 
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-pmd-plugin/job/master/
+Open an issue to discuss larger changes first, then send a pull request from a 
fork with tests
+(a unit test or an integration test under `src/it`) and run `mvn -Prun-its 
verify` before you push.
+See [Contributing to Apache 
Maven](https://maven.apache.org/guides/development/guide-helping.html) and the
+[developer mailing list](https://maven.apache.org/mailing-lists.html).
diff --git a/src/site/markdown/examples/cpdCsharp.md.vm 
b/src/site/markdown/examples/cpdCsharp.md.vm
index b0aa6f1..3d9ca1b 100644
--- a/src/site/markdown/examples/cpdCsharp.md.vm
+++ b/src/site/markdown/examples/cpdCsharp.md.vm
@@ -26,7 +26,7 @@ under the License.
 
 # Finding duplicated code in C\#
 
-By default, the maven-pmd-plugin only supports the languages Java, JavaScript 
and JSP. But [CPD supports many more 
languages](https://pmd.github.io/latest/pmd_userdocs_cpd.html#supported-languages),
 e.g. C#. In order to enable C# in your build, you need to configure several 
parts:
+By default, the maven-pmd-plugin only supports the languages Java, JavaScript 
and JSP. But [CPD supports many more 
languages](https://docs.pmd-code.org/latest/pmd_userdocs_cpd.html#supported-languages),
 e.g. C#. In order to enable C# in your build, you need to configure several 
parts:
 
 - Add an additional plugin dependency for c# (pmd-cs module)
 - Select the language `cs`.
diff --git a/src/site/markdown/examples/javascriptReport.md.vm 
b/src/site/markdown/examples/javascriptReport.md.vm
index ce29e07..d9cd066 100644
--- a/src/site/markdown/examples/javascriptReport.md.vm
+++ b/src/site/markdown/examples/javascriptReport.md.vm
@@ -32,7 +32,7 @@ The example assumes that the JavaScript source code is stored 
in the subdirector
 
 Note that you have to make sure that you configure `compileSourceRoots` and 
`includes`, so that PMD finds the JavaScript files.
 
-See [JavaScript Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_ecmascript.html) for 
the list of available rules.
+See [JavaScript Rule 
Index](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_ecmascript.html)
 for the list of available rules.
 
 ```xml
 <project>
@@ -70,5 +70,3 @@ See [JavaScript Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_ec
   ...
 </project>
 ```
-
-**Note:** Configuring `compileSourceRoots` only works with Maven 3.3.9 and 
later. For older versions, you'll need to use _build-helper-maven-plugin_ with 
the `add-source` goal in order to add the additional source directories, so 
that PMD finds the JavaScript files.
diff --git a/src/site/markdown/examples/jspReport.md.vm 
b/src/site/markdown/examples/jspReport.md.vm
index c5a877a..61e5cc6 100644
--- a/src/site/markdown/examples/jspReport.md.vm
+++ b/src/site/markdown/examples/jspReport.md.vm
@@ -32,7 +32,7 @@ The example assumes that the JSP source code is stored in 
various subdirectories
 
 Note that you have to make sure that you configure `compileSourceRoots` and 
`includes`, so that PMD finds the JSP files.
 
-See [JSP Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_jsp.html) for a 
complete list of available rules.
+See [JSP Rule 
Index](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_jsp.html) for 
a complete list of available rules.
 
 ```xml
 <project>
@@ -72,5 +72,3 @@ See [JSP Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_jsp.html)
   ...
 </project>
 ```
-
-**Note:** Configuring `compileSourceRoots` only works with Maven 3.3.9 and 
later. For older versions, you'll need to use _build-helper-maven-plugin_ with 
the `add-source` goal in order to add the additional source directories, so 
that PMD finds the JSP files.
diff --git a/src/site/markdown/examples/multi-module-config.md.vm 
b/src/site/markdown/examples/multi-module-config.md.vm
index faf3a7e..86de844 100644
--- a/src/site/markdown/examples/multi-module-config.md.vm
+++ b/src/site/markdown/examples/multi-module-config.md.vm
@@ -84,7 +84,7 @@ A sample `pmd-ruleset.xml` could look like this:
 <ruleset name="whizbang PMD ruleset"
     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";>
+    xsi:schemaLocation="http://pmd.sourceforge.net/ruleset/2.0.0 
https://pmd.sourceforge.io/ruleset_2_0_0.xsd";>
 
     <description>
         This ruleset defines the PMD rules for project "whizbang".
@@ -105,11 +105,11 @@ A sample `pmd-ruleset.xml` could look like this:
     <rule ref="category/java/errorprone.xml/AvoidUsingOctalValues" />
     <rule ref="category/java/errorprone.xml/BrokenNullCheck" />
 
-    <!-- many more rules are available at 
https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_java.html -->
+    <!-- many more rules are available at 
https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_java.html -->
 </ruleset>
 ```
 
-The ruleset references some built-in rules. For more information about 
rulesets, see [Making 
Rulesets](https://pmd.github.io/pmd-${pmdVersion}/pmd_userdocs_making_rulesets.html)
 and [Using Rule Sets](./usingRuleSets.html).
+The ruleset references some built-in rules. For more information about 
rulesets, see [Making 
Rulesets](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_userdocs_making_rulesets.html)
 and [Using Rule Sets](./usingRuleSets.html).
 
 Configure the other projects to use it
 --------------------------------------
diff --git a/src/site/markdown/examples/targetJdk.md.vm 
b/src/site/markdown/examples/targetJdk.md.vm
index 07c8aa8..bd03d0b 100644
--- a/src/site/markdown/examples/targetJdk.md.vm
+++ b/src/site/markdown/examples/targetJdk.md.vm
@@ -27,7 +27,7 @@ under the License.
 
 # Target JDK
 
-There is a configuration element in the PMD plugin that lets you set which 
[target JDK](../pmd-mojo.html#targetJdk) your Java code will be compiled for. 
Often you want this to be in sync with the configuration for 
maven-compiler-plugin. The best practice for this is to set up the wellknown 
property `maven.compiler.target` and the rest will work automatically. 
Alternatively, you can set it manually:
+There is a configuration element in the PMD plugin that lets you set which 
[target JDK](../pmd-mojo.html#targetJdk) your Java code will be compiled for. 
Often you want this to be in sync with the configuration for 
maven-compiler-plugin. `targetJdk` defaults to the property 
`maven.compiler.source`, so a project that sets that property needs no further 
configuration. A project that sets only `maven.compiler.release` must pass it 
on explicitly, for example `<targetJdk>${esc.d}{maven.compile [...]
 
 ```xml
 <project>
@@ -47,6 +47,8 @@ There is a configuration element in the PMD plugin that lets 
you set which [targ
 </project>
 ```
 
+The value must be a Java version that PMD supports. PMD ${pmdVersion} lists 
the versions it accepts, including the `-preview` variants for the latest two 
Java releases, in [Java 
support](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_languages_java.html).
 To analyze code for a newer Java release, [upgrade PMD at 
runtime](./upgrading-PMD-at-runtime.html).
+
 Since version 3.29.0, the plugin automatically uses the value of `targetJdk` 
to resolve the Java platform classes via a matching toolchain. For [type 
resolution](../pmd-mojo.html#typeResolution), PMD reads the class files of both 
dependencies and the Java platform. If the wrong Java platform is selected, 
this might result in false positive and/or false negative violations. It is 
therefore important to have a toolchain configured with a version matching 
targetJdk.
 
 Example `${user.home}/.m2/toolchains.xml`:
@@ -78,4 +80,4 @@ Since version 3.29.0 of the PMD plugin, `targetJdk` is used 
to resolve the JDK f
 
 To set this up, refer to the [Guide to Using 
Toolchains](/guides/mini/guide-using-toolchains.html), which makes use of the 
[Maven Toolchains Plugin](/plugins/maven-toolchains-plugin/).
 
-With the maven-toolchains-plugin you configure 1 default JDK toolchain for all 
related maven-plugins. Since maven-pmd-plugin 3.14.0 when using with Maven 
3.3.1+ it is also possible to give the plugin its own toolchain, which can be 
useful in case of different JDK calls per execution block (e.g. the test 
sources require a different JDK compared to the main sources).
+With the maven-toolchains-plugin you configure 1 default JDK toolchain for all 
related maven-plugins. Since maven-pmd-plugin 3.14.0 it is also possible to 
give the plugin its own toolchain with the 
[jdkToolchain](../pmd-mojo.html#jdkToolchain) parameter, which can be useful in 
case of different JDK calls per execution block (e.g. the test sources require 
a different JDK compared to the main sources).
diff --git a/src/site/markdown/examples/upgrading-PMD-at-runtime.md.vm 
b/src/site/markdown/examples/upgrading-PMD-at-runtime.md.vm
index 99eed72..849f5ed 100644
--- a/src/site/markdown/examples/upgrading-PMD-at-runtime.md.vm
+++ b/src/site/markdown/examples/upgrading-PMD-at-runtime.md.vm
@@ -88,16 +88,16 @@ Here's a historical overview about the default PMD version 
used:
 | [3.26.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.26.0/) 
|  [7.7.0](https://docs.pmd-code.org/pmd-doc-7.7.0/)  |
 | [3.24.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.24.0/) 
|  [7.3.0](https://docs.pmd-code.org/pmd-doc-7.3.0/)  |
 | [3.22.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.22.0/) 
|  [7.0.0](https://docs.pmd-code.org/pmd-doc-7.0.0/)  |
-| [3.21.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.21.0/) 
|     [6.55.0](https://pmd.github.io/pmd-6.55.0/)     |
-| [3.20.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.20.0/) 
|     [6.53.0](https://pmd.github.io/pmd-6.53.0/)     |
-| [3.19.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.19.0/) 
|     [6.49.0](https://pmd.github.io/pmd-6.49.0/)     |
-| [3.18.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.18.0/) 
|     [6.48.0](https://pmd.github.io/pmd-6.48.0/)     |
-| [3.17.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.17.0/) 
|     [6.46.0](https://pmd.github.io/pmd-6.46.0/)     |
-| [3.16.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.16.0/) 
|     [6.42.0](https://pmd.github.io/pmd-6.42.0/)     |
-| [3.15.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.15.0/) 
|     [6.38.0](https://pmd.github.io/pmd-6.38.0/)     |
-| [3.14.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.14.0/) 
|     [6.29.0](https://pmd.github.io/pmd-6.29.0/)     |
-| [3.13.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.13.0/) 
|     [6.21.0](https://pmd.github.io/pmd-6.21.0/)     |
-| [3.12.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.12.0/) 
|     [6.13.0](https://pmd.github.io/pmd-6.13.0/)     |
+| [3.21.2](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.21.2/) 
|     [6.55.0](https://pmd.sourceforge.io/pmd-6.55.0/)     |
+| [3.20.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.20.0/) 
|     [6.53.0](https://pmd.sourceforge.io/pmd-6.53.0/)     |
+| [3.19.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.19.0/) 
|     [6.49.0](https://pmd.sourceforge.io/pmd-6.49.0/)     |
+| [3.18.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.18.0/) 
|     [6.48.0](https://pmd.sourceforge.io/pmd-6.48.0/)     |
+| [3.17.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.17.0/) 
|     [6.46.0](https://pmd.sourceforge.io/pmd-6.46.0/)     |
+| [3.16.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.16.0/) 
|     [6.42.0](https://pmd.sourceforge.io/pmd-6.42.0/)     |
+| [3.15.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.15.0/) 
|     [6.38.0](https://pmd.sourceforge.io/pmd-6.38.0/)     |
+| [3.14.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.14.0/) 
|     [6.29.0](https://pmd.sourceforge.io/pmd-6.29.0/)     |
+| [3.13.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.13.0/) 
|     [6.21.0](https://pmd.sourceforge.io/pmd-6.21.0/)     |
+| [3.12.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.12.0/) 
|     [6.13.0](https://pmd.sourceforge.io/pmd-6.13.0/)     |
 | [3.11.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.11.0/) 
|   [6.8.0](https://pmd.sourceforge.io/pmd-6.8.0/)    |
 | [3.10.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.10.0/) 
|   [6.4.0](https://pmd.sourceforge.io/pmd-6.4.0/)    |
 |  [3.9.0](https://maven.apache.org/plugins-archives/maven-pmd-plugin-3.9.0/)  
|   [6.0.1](https://pmd.sourceforge.io/pmd-6.0.1/)    |
diff --git a/src/site/markdown/examples/usingRuleSets.md.vm 
b/src/site/markdown/examples/usingRuleSets.md.vm
index 9bb926d..ac393d2 100644
--- a/src/site/markdown/examples/usingRuleSets.md.vm
+++ b/src/site/markdown/examples/usingRuleSets.md.vm
@@ -30,17 +30,15 @@ The PMD plugin ships a default rule set, that has various 
rules enabled. The rul
 
 There are many more rules available and bundled in the PMD code analysis tool:
 
-- [Java Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_java.html)
-- [JavaScript Rule 
Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_ecmascript.html)
-- [JSP Rule Index](https://pmd.github.io/pmd-${pmdVersion}/pmd_rules_jsp.html)
+- [Java Rule 
Index](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_java.html)
+- [JavaScript Rule 
Index](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_ecmascript.html)
+- [JSP Rule 
Index](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_rules_jsp.html)
 
-To use other rule sets, you can configure it in the plugin as shown below. The 
rule sets may reside in the classpath, filesystem or at a URL. For rule sets 
that are bundled with the PMD tool, you do not need to specify the absolute 
path of the file. It will be resolved by the plugin. But if the rule set is a 
custom rule set, you need to specify its absolute path.
+To use other rule sets, you can configure it in the plugin as shown below. The 
rule sets may reside in the classpath, filesystem or at a URL. Rule sets 
bundled with PMD are found on the classpath. A relative file path is resolved 
against the directory of the project's POM, then against the directory where 
the build was started.
 
-See [Making 
Rulesets](https://pmd.github.io/pmd-${pmdVersion}/pmd_userdocs_making_rulesets.html)
 if you want to create your own custom ruleset.
+See [Making 
Rulesets](https://docs.pmd-code.org/pmd-doc-${pmdVersion}/pmd_userdocs_making_rulesets.html)
 if you want to create your own custom ruleset.
 
-**Note:** Starting with PMD 5.0 and Maven PMD Plugin 3.0 the paths to the 
bundled rule sets for the Java language were changed from `/rulesets/xyz.xml` 
to `/rulesets/java/xyz.xml`. So when upgrading to Maven PMD Plugin 3.0 you may 
need to alter your plugin configuration.
-
-**Note:** Starting with PMD 6.0.0 and Maven PMD Plugin 3.9.0, the rules have 
been reorganized into categories, e.g. `/category/java/bestpractices.xml`. So 
when upgrading to Maven PMD Plugin 3.9.0 you should review your plugin 
configuration and/or custom ruleset.
+**Note:** Since PMD 6.0.0, the bundled rules are organized into categories, 
for example `/category/java/bestpractices.xml`. PMD 7 renamed, merged or 
removed a number of rules; when you upgrade from PMD 6, check custom rulesets 
against the [Migration Guide for PMD 
7](https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pmd7.html).
 
 ```xml
 <project>
@@ -55,10 +53,10 @@ See [Making 
Rulesets](https://pmd.github.io/pmd-${pmdVersion}/pmd_userdocs_makin
           <rulesets>
             <!-- A rule set, that comes bundled with PMD -->
             <ruleset>/category/java/bestpractices.xml</ruleset>
-            <!-- Custom local file system rule set -->
-            <ruleset>d:\rulesets\strings.xml</ruleset>
+            <!-- Custom rule set in the project directory -->
+            <ruleset>config/pmd/strings.xml</ruleset>
             <!-- Custom remote rule set accessed via a URL -->
-            <ruleset>http://localhost/design.xml</ruleset>
+            
<ruleset>https://raw.githubusercontent.com/apache/maven-pmd-plugin/master/src/main/resources/rulesets/java/maven-pmd-plugin-default.xml</ruleset>
           </rulesets>
         </configuration>
       </plugin>
@@ -72,7 +70,7 @@ See [Making 
Rulesets](https://pmd.github.io/pmd-${pmdVersion}/pmd_userdocs_makin
 
 This is an excerpt of the ruleset 
`/rulesets/java/maven-pmd-plugin-default.xml`. It contains only rules for Java. 
If you use a different language, you'll need to specify your own custom ruleset.
 
-The current version of the ruleset can be found in version control: 
[https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=blob_plain;f=src/main/resources/rulesets/java/maven-pmd-plugin-default.xml;hb=HEAD](https://gitbox.apache.org/repos/asf?p=maven-pmd-plugin.git;a=blob_plain;f=src/main/resources/rulesets/java/maven-pmd-plugin-default.xml;hb=HEAD)
+The current version of the ruleset is in the source repository: 
[maven-pmd-plugin-default.xml](https://github.com/apache/maven-pmd-plugin/blob/master/src/main/resources/rulesets/java/maven-pmd-plugin-default.xml).
 
 ```xml
     <rule ref="category/java/bestpractices.xml/AvoidUsingHardCodedIP" />
diff --git a/src/site/markdown/faq.md b/src/site/markdown/faq.md
index e576ff5..07aa04f 100644
--- a/src/site/markdown/faq.md
+++ b/src/site/markdown/faq.md
@@ -38,6 +38,11 @@ under the License.
 Yes, each report supports a skip parameter which you can pass on the command 
line, `-Dpmd.skip=true` and
 `-Dcpd.skip=true` respectively.
 
+To make the PMD analysis itself faster or lighter, set the number of analysis 
threads with the
+[executionThreads](pmd-mojo.html#executionThreads) parameter 
(`-Dpmd.executionThreads=...`). PMD uses one
+thread per CPU core by default; a lower value such as `0.5C` or `2` leaves 
cores free for the other modules of
+a parallel build (`mvn -T`).
+
 <a id="xref_links"></a>
 
 ### How can I generate links to the JXR cross-referenced source?
@@ -48,7 +53,7 @@ on by default).
 Then, the jxr plugin has to run first so that the links can be picked up by 
the pmd report. If you run from
 the command line, use `mvn jxr:jxr pmd:pmd`, or if you want the reports 
generated by the site plugin,
 configure the jxr plugin in your reporting section, see
-[JXR usage](http://maven.apache.org/plugins/maven-jxr-plugin/usage.html).
+[JXR usage](https://maven.apache.org/plugins/maven-jxr-plugin/usage.html).
 
 <a id="no_report_in_site"></a>
 
@@ -56,8 +61,8 @@ configure the jxr plugin in your reporting section, see
 
 If there are no violations, then by default no reports are created and the 
entire PMD or CPD section is not
 rendered in the site. To change this behaviour, set the
-[skipEmptyReport for PMD](pmd-mojo#skipEmptyReport) or
-[skipEmptyReport for CPD](cpd-mojo#skipEmptyReport) to `false`
+[skipEmptyReport for PMD](pmd-mojo.html#skipEmptyReport) or
+[skipEmptyReport for CPD](cpd-mojo.html#skipEmptyReport) to `false`
 
 <a id="violations_failures_warnings"></a>
 
@@ -97,7 +102,7 @@ changes between versions. For example, 
`java.util.concurrent.ExecutorService` ha
 since Java 19 - the rule 
[CloseResource](https://docs.pmd-code.org/latest/pmd_rules_java_errorprone.html#closeresource)
 can only detect this correctly if PMD resolves types against that Java version 
or later.
 Since version 3.29.0, the plugin automatically adds the Java platform classes 
to the auxclasspath,
-so that they are also available for type resolution.. The property 
[`targetJdk`](pmd-mojo.html#targetJdk)
+so that they are also available for type resolution. The property 
[`targetJdk`](pmd-mojo.html#targetJdk)
 determines the Java version to use, and a corresponding toolchain is selected. 
If none is available,
 a warning is issued and the current Java runtime is used instead, which may 
lead to false positive or
 false negative findings. See also [Target JDK and 
Toolchains](examples/targetJdk.html).
diff --git a/src/site/markdown/index.md.vm b/src/site/markdown/index.md.vm
index 28ef966..c67c4af 100644
--- a/src/site/markdown/index.md.vm
+++ b/src/site/markdown/index.md.vm
@@ -26,11 +26,26 @@ under the License.
 
 # ${project.name}
 
-The PMD Plugin allows you to automatically run the 
[PMD](https://pmd.github.io/) code analysis tool on your project's source code 
and generate a site report with its results. It also supports the separate 
Copy/Paste Detector tool (or CPD) distributed with PMD.
+The PMD Plugin runs the [PMD](https://pmd.github.io/) static code analyzer and 
its Copy/Paste Detector (CPD) on your project's source code. It can fail the 
build on violations or duplicated code, and it can publish both results as 
reports on your project site.
 
-This version of Maven PMD Plugin uses PMD ${pmdVersion} and requires Java 
${javaVersion}. See [Upgrading PMD at 
Runtime](./examples/upgrading-PMD-at-runtime.html) for more information.
+This version uses PMD ${pmdVersion} and needs Maven 
${project.prerequisites.maven} or later running on Java ${javaVersion} or 
later. To use a newer PMD release, see [Upgrading PMD at 
Runtime](./examples/upgrading-PMD-at-runtime.html).
 
-The plugin accepts configuration parameters that can be used to customize the 
execution of the PMD tool.
+The most common tasks are:
+
+- Check the code against the default PMD rules and fail the build on 
violations. Bind the goal into your build as shown in [Violation 
Checking](./examples/violationChecking.html), or run it directly:
+
+    ```shell
+    mvn compile pmd:check
+    ```
+
+- Find duplicated code and fail the build when CPD reports any:
+
+    ```shell
+    mvn pmd:cpd-check
+    ```
+
+- Add the PMD and CPD reports to the project site by declaring the plugin in 
the `<reporting>` section (see [Usage](./usage.html)), then run `mvn site`.
+- Use your own rules instead of the default ruleset, as described in [Using 
Rule Sets](./examples/usingRuleSets.html).
 
 Goals Overview
 --------------
@@ -41,7 +56,7 @@ This plugin has the following goals:
 - [pmd:aggregate-pmd](./aggregate-pmd-mojo.html) creates a PMD site report in 
an **aggregator** project based on the rulesets and configuration set in the 
plugin. It can also generate a pmd output file aside from the site report in 
any of the following formats: xml, csv or txt.
 - [pmd:aggregate-pmd-no-fork](./aggregate-pmd-no-fork-mojo.html) creates a PMD 
site report in an **aggregator** project without forking the `test-compile` 
phase again.
 - [pmd:cpd](./cpd-mojo.html) creates a report for PMD's Copy/Paste Detector 
(CPD) tool. It can also generate a cpd results file in any of these formats: 
xml, csv or txt.
-- [pmd:aggregate-cpd](./aggregate-cpd-mojo) creates a report for PMD's 
Copy/Paste Detector (CPD) tool in an **aggregator** project. It can also 
generate a cpd results file in any of these formats: xml, csv or txt.
+- [pmd:aggregate-cpd](./aggregate-cpd-mojo.html) creates a report for PMD's 
Copy/Paste Detector (CPD) tool in an **aggregator** project. It can also 
generate a cpd results file in any of these formats: xml, csv or txt.
 - [pmd:check](./check-mojo.html) fails the build if there were any PMD 
violations in the source code. This goal invokes automatically `pmd:pmd` prior 
to executing itself.
 - [pmd:aggregate-pmd-check](./aggregate-pmd-check-mojo.html) fails the build 
in an **aggregator** project if there were any PMD violations in the source 
code. This goal invokes automatically `pmd:aggregate-pmd` prior to executing 
itself.
 - [pmd:cpd-check](./cpd-check-mojo.html) fails the build if there were any CPD 
violations in the source code. This goal invokes automatically `pmd:cpd` prior 
to executing itself.
@@ -50,11 +65,9 @@ This plugin has the following goals:
 Usage
 -----
 
-General instructions on how to use the PMD Plugin can be found on the [usage 
page](./usage.html). Some more specific use cases are described in the examples 
given below.
-
-In case you still have questions regarding the plugin's usage, please have a 
look at the [FAQ](./faq.html) and feel free to contact the [user mailing 
list](./mailing-lists.html). The posts to the mailing list are archived and 
could already contain the answer to your question as part of an older thread. 
Hence, it is also worth browsing/searching the [mail 
archive](./mailing-lists.html).
+General instructions on how to use the PMD Plugin can be found on the [usage 
page](./usage.html). Some more specific use cases are described in the examples 
given below. If you still have questions, see the [FAQ](./faq.html) or ask on 
the [user mailing list](./mailing-lists.html).
 
-If you feel like the plugin is missing a feature or has a defect, you can file 
a feature request or bug report in our [issue 
tracker](./issue-management.html). When creating a new issue, please provide a 
comprehensive description of your concern. Especially for fixing bugs it is 
crucial that the developers can reproduce your problem. For this reason, entire 
debug logs, POMs or most preferably little demo projects attached to the issue 
are very much appreciated. Of course, patches are wel [...]
+To report a defect or request a feature, open an issue in the [issue 
tracker](./issue-management.html) with steps to reproduce, ideally a small demo 
project. To contribute a fix, see the [source repository](./scm.html) and the 
[guide to helping with 
Maven](https://maven.apache.org/guides/development/guide-helping.html).
 
 Upgrading Notes
 ---------------
@@ -65,12 +78,11 @@ Upgrading Notes
 
 #[[### 3.22.0]]#
 
-- Starting with Maven PMD Plugin 3.22.0, the plugin requires PMD version 7.0.0 
or higher. PMD 7.0.0 switched to SLF4J and since Maven 3.1.0+ SLF4J is the 
default logging API. Logs from PMD are now always shown and cannot be disabled 
at runtime after maven has started. The property `showPmdLog` makes no sense 
anymore and is deprecated now. See [Maven 
Logging](https://maven.apache.org/maven-logging.html) for how to configure 
logging. For disabling PMD logs, you'd need to start maven with ` [...]
-- The upgrade from PMD 6 to PMD 7.0.0 is a major version change. If you use 
the default ruleset from Maven PMD Plugin, then everything should just work. 
But if you use a custom ruleset, you most likely need to review your ruleset 
and migrate it to PMD 7. Rules might have been renamed or replaced. See 
[Detailed Release Notes for PMD 
7](https://docs.pmd-code.org/latest/pmd_release_notes_pmd7.html) and [Migration 
Guide for PMD 7](https://docs.pmd-code.org/latest/pmd_userdocs_migrating_to_pm 
[...]
+- Starting with Maven PMD Plugin 3.22.0, the plugin requires PMD version 7.0.0 
or higher. PMD 7 logs through SLF4J, which Maven uses for its own logging. Logs 
from PMD are now always shown and cannot be disabled at runtime after maven has 
started. The property `showPmdLog` makes no sense anymore and is deprecated 
now. See [Maven Logging](https://maven.apache.org/maven-logging.html) for how 
to configure logging. For disabling PMD logs, you'd need to start maven with 
`MAVEN_OPTS=-Dorg.slf4 [...]
+- The upgrade from PMD 6 to PMD 7.0.0 is a major version change. If you use 
the default ruleset from Maven PMD Plugin, then everything should just work. 
But if you use a custom ruleset, you most likely need to review your ruleset 
and migrate it to PMD 7. Rules might have been renamed or replaced. See 
[Detailed Release Notes for PMD 
7](https://docs.pmd-code.org/pmd-doc-7.0.0/pmd_release_notes_pmd7.html) and 
[Migration Guide for PMD 
7](https://docs.pmd-code.org/latest/pmd_userdocs_migratin [...]
 - If you currently override the dependency to PMD ([Upgrading PMD at 
Runtime](./examples/upgrading-PMD-at-runtime.html)) make sure to upgrade PMD as 
well to 7.0.0 or later when upgrading the Maven PMD Plugin.
-#[[### 3.9.0]]#
 
-- Starting with PMD 6.0.0 and Maven PMD Plugin 3.9.0, the rules have been 
reorganized into categories, e.g. `/category/java/bestpractices.xml`. So when 
upgrading to Maven PMD Plugin 3.9.0 you should review your plugin configuration 
and/or custom ruleset. See [Using Rule Sets](./examples/usingRuleSets.html) for 
more information.
+<a id="a3.9.0"></a>
 
 Examples
 --------
diff --git a/src/site/markdown/usage.md.vm b/src/site/markdown/usage.md.vm
index 0a99776..5e2a1cf 100644
--- a/src/site/markdown/usage.md.vm
+++ b/src/site/markdown/usage.md.vm
@@ -68,13 +68,13 @@ You can also explicitly execute the PMD plugin and generate 
the same report by s
 
 The PMD and CPD reports share the same configuration. For example, the 
following tells Maven to run the PMD and CPD report as part of the site report 
generation.
 
-The reports will link directly to the cross-referenced source if you enable 
this with the `linkXRef` parameter. See the [JXR 
plugin](http://maven.apache.org/plugins/maven-jxr-plugin/) for more details.
+The reports link to the cross-referenced source when the [JXR 
plugin](https://maven.apache.org/plugins/maven-jxr-plugin/) report is also 
configured; the `linkXRef` parameter (on by default) controls this.
 
-If your source uses a non-default encoding, you can use the `inputEncoding` 
parameter to tell Maven which encoding to use when reading the java source. 
Note also the ability to exclude source which you want to ignore.
+The plugin reads the sources with the encoding set in 
`project.build.sourceEncoding`. Note also the ability to exclude source which 
you want to ignore.
 
 You can configure the minimum code size which trips the CPD. The default of 
`100` tokens corresponds to approximately 5-10 lines of code.
 
-Since PMD parses the Java source, it needs to know which Java version to use. 
The following is a possible configuration:
+Since PMD parses the Java source, it needs to know which Java version to use. 
The `targetJdk` parameter defaults to `maven.compiler.source`; see [Target JDK 
and Toolchains](./examples/targetJdk.html). The following is a possible 
configuration:
 
 ```xml
 <project>
@@ -86,10 +86,9 @@ Since PMD parses the Java source, it needs to know which 
Java version to use. Th
         <artifactId>maven-pmd-plugin</artifactId>
         <version>${project.version}</version>
         <configuration>
-          <linkXref>true</linkXref>
-          <inputEncoding>utf-8</inputEncoding>
+          <linkXRef>true</linkXRef>
           <minimumTokens>100</minimumTokens>
-          <targetJdk>1.5</targetJdk>
+          <targetJdk>17</targetJdk>
           <excludes>
             <exclude>**/*Bean.java</exclude>
             <exclude>**/generated/*.java</exclude>

Reply via email to