3.0.1

This is a minor release to downgrade maven-site-plugin slightly to where it supports doxia <2.0. Without this, certain reports/pages would have improperly rendered i18n getters exposed.

3.0.0

This is considered a major release as:

1. You must use at least maven 3.6.3
   This is to support maven plugins compiled against later mojo apis. More importantly, the latest version of maven (3.9.9 at time of this writing) also works, whereas before certain plugins could not execute with 3.9.X+
2. The PMD 7 upgrade more strictly enforces some rules
   The default ruleset included in com.salesforce.maven:MavenAnalysisConf is the same in spirit, it is not intending to enforce any new rules or remove enforcement of prior rules, however the implementation of that enforcement is largely more strict with PMD version 7 than it was in the prior version 6. Specifically, you may find upgrading to flag LooseCoupling more than before, as in the latest version of the rule it traverses more deeply into nested classes to determine if there is a common interface that could have been used instead. You may find other rules which similarly flag where they didn't before under PMD 6, even though the fundamental rule is not new.
3. The PGP key signing all artifacts has been rotated. The new public key is 1E9A97BBB9FAB0E26833548E323D47325848C755

Additionally, there are a great many plugin upgrades which have been tested to interoperate with eachother, and build with and compile to Java 8 and Java 21. If you override any plugin versions, ensure that:

• your execution works with at least maven 3.6.3
• any reporting plugins interoperate with the maven-site-plugin, e.g. mvn org.apache.maven.plugins:maven-site-plugin:run completes and you can navigate to rendered pages

MavenParent-1.0.19

Revert pmd-java bump