If the pattern does not match for a path starting with / (e.g. when the prefix/libs is forgotten) in the option whitelistedResourcePathPatterns it will never match and does not lead to the desired whitelisting. In such a case at least a WARN should be emitted.

Using AEM 6.5.13 and the latest aem-content-classifications jar, we get:

[ERROR] ValidationViolation: "netcentric-aem-classification: Element with name "jcr:root" inherits from resource 'granite/ui/components/coral/foundation/form/field' which is marked as 'granite:InternalArea (derived from parent content classification)'. It therefore violates the content classification!", filePath=jcr_root/apps/website/test/.content.xml, nodePath=/apps/website/test, line=5, column=79

But, AEM's repository says:

• /libs/granite/ui/components/coral/foundation/form/field = granite:PublicArea
• /libs/granite/ui/components/coral/foundation/form = granite:FinalArea
• /libs/granite/ui/components/coral/foundation = granite:FinalArea
• /libs/granite/ui/components/coral = granite:FinalArea
• /libs/granite/ui/components = granite:FinalArea
• /libs/granite/ui = No classification
• /libs/granite = No classification
• /libs = No classification

What is the recommended approach to using this tooling? To reference the JAR files, or to always generate the maps yourself and reference the generated maps? (When we generate a new map based on our 6.5.13 instance, we do get the correct classifications, where it also says that /libs/granite/ui/components/coral/foundation/form/field is PUBLIC, instead fo INTERNAL.)

Despite the README stating that you can use the option whitelistedResourcePathPatterns to whitelist resource paths, the option must be named whitelistedResourcePathsPatterns.

Currently if one referenced resource ends with a slash the following exception is logged

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  49.602 s
[INFO] Finished at: 2020-03-12T09:33:12+01:00
[INFO] ------------------------------------------------------------------------
[DEBUG] No threads registered for execution at the end of the build
[ERROR] Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package (default-validate-package) on project nc-website-components-package: Execution default-validate-package of goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package failed: Resource path must not end with '/' but is '..../' -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package (default-validate-package) on project nc-website-components-package: Execution default-validate-package of goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package failed: Resource path must not end with '/' but is '/libs/core/wcm/components/teaser/v1/teaser/

This error message must be improved to at least emit the file path where the error occurred!
Also the debug log level does not help much as the previous output is
[DEBUG] ValidationViolation: "Validating jcr file '<some jcr file>'..." which is not the failing file but the previous one!

The issue can be easily reproduced by setting the value sling:resourceSuperType on a component definition to a value like core/wcm/components/teaser/v1/teaser/

The situation will improve with the upcoming FileVault 3.4.4 (https://issues.apache.org/jira/browse/JCRVLT-406)

Instead the whitellistedResourcePathPattern should refer to the path where the overlay is located (i.e. starting with "/apps")

Currently a violation in a DocView XML leads to the following message:

[WARNING] ValidationViolation: "netcentric-aem-classification: Element with name "{}test" inherits from resource '...' which is marked as 'granite:InternalArea (derived from parent content classification)'. It therefore violates the content classification!", filePath=... nodePath=.., line=5, column=82

The element name has currently the JCR Expanded Form which is not really common for XML. Therefore it should be emitted in a more human readable format.
Unfortunately the prefix used for the namespace URI is unknown to the validator, so it should just

• emit the local name only in case the namespace is empty
• emit the local name followed by the namespace URI in brackets in case the namespace is not empty