Update changelog, refs #603

docs/pages/release_notes.md

@@ -243,6 +243,9 @@ The cache will now detect changes to the JARs referenced in the `auxclasspath` i
 and order. This means that if you are referencing a JAR you are overwriting in some way, the incremental analysis can
 now detect it and invalidate it's cache to avoid false reports.
 
+Similarly, any changes to the execution classpath of PMD will invalidate the cache. This means that if you have custom
+rules packaged in a jar, any changes to it will invalidate the cache automatically.
+
 We have also improved logging on the analysis code, allowing better insight into how the cache is performing,
 under debug / verbose builds you can even see individual hits / misses to the cache (and the reason for any miss!)
 
@@ -276,6 +279,7 @@ a warning will now be produced suggesting users to adopt it for better performan
     *   [#510](https://github.com/pmd/pmd/issues/510): \[java] Typeresolution fails on a simple primary when the source is loaded from a class literal
     *   [#527](https://github.com/pmd/pmd/issues/527): \[java] Lombok getter annotation on enum is not recognized correctly
     *   [#534](https://github.com/pmd/pmd/issues/534): \[java] NPE in MethodTypeResolution for static methods
+    *   [#603](https://github.com/pmd/pmd/issues/603): \[core] incremental analysis should invalidate upon Java rule plugin changes
     *   [#650](https://github.com/pmd/pmd/issues/650): \[java] ProcesingError analyzing code under 5.8.1
 *   java-basic
     *   [#565](https://github.com/pmd/pmd/pull/565): \[java] False negative on DontCallThreadRun when extending Thread