You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: aem-classification-validator/README.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,10 @@ The following options are supported apart from the default settings mentioned in
14
14
15
15
Option | Mandatory | Description
16
16
--- | --- | ---
17
-
maps | yes | a comma-separated list of URLs specifying the source for a classification map. Each URL might use the protocols `file:`, for file-based classification maps, `http(s):` for classification maps in the internet or `tccl:` for classification maps being provided via the ThreadContextClassloader. The latter is especially useful with Maven as the TCCL during the execution of a goal of a Maven Plugin is the [Maven Plugin Classpath][4].
18
-
whitelistedResourcePathPatterns | no | a comma-separated list of regular expressions matching an absolute resource path which should not be reported (no matter if its usage violates content classifications or not). The path is referring to the referenced/inherited/overlaid resource path (not the path containing the reference/supertype/overlay).
19
-
severitiesPerClassification | no | the severity per classification (this will overwrite the default severity which otherwise used for all classifications). The format is `<classification>=<severity>{,<classification>=<severity>}`, where `classification` is one of `INTERNAL`, `INTERNAL_DEPRECATED_ANNOTATION`, `INTERNAL_DEPRECATED`, `FINAL` or `ABSTRACT` and `severity` is one of `DEBUG`, `INFO`, `WARN` or `ERROR`.
17
+
maps | yes | a comma-separated list of URLs specifying the source for a classification map. Each URL might use the protocols `file:`, for file-based classification maps, `http(s):` for classification maps in the internet or `tccl:` for classification maps being provided via the ThreadContextClassloader. The latter is especially useful with Maven as the TCCL during the execution of a goal of a Maven Plugin is the [Maven Plugin Classpath][4].
18
+
whitelistedResourcePathPatterns | no | a comma-separated list of regular expressions matching an absolute resource path which should not be reported (no matter if its usage violates content classifications or not). The path is referring to the referenced/inherited/overlaid resource path (not the path containing the reference/supertype/overlay).
19
+
whitelistedSourcePathPatterns | no | a comma-separated list of regular expressions matching an absolute source path which should not be reported (no matter if its usage violates content classifications or not). Use this if you know there is an issue with classification for a specific component, but you don't want the problem to spread to other components.
20
+
severitiesPerClassification | no | the severity per classification (this will overwrite the default severity which otherwise used for all classifications). The format is `<classification>=<severity>{,<classification>=<severity>}`, where `classification` is one of `INTERNAL`, `INTERNAL_DEPRECATED_ANNOTATION`, `INTERNAL_DEPRECATED`, `FINAL` or `ABSTRACT` and `severity` is one of `DEBUG`, `INFO`, `WARN` or `ERROR`.
20
21
21
22
All validation messages are emitted with the [`defaultSeverity`][2]
22
23
@@ -33,16 +34,16 @@ The file is a CSV serialization of the map where each line represents one item i
33
34
<path>,<classification>(,<remark>)
34
35
```
35
36
36
-
where `classification` is one of
37
+
where `classification` is one of
37
38
38
39
1.`INTERNAL`
39
40
2.`INTERNAL_DEPRECATED_ANNOTATION`, same restrictions as `INTERNAL` but due to being marked as deprecated via some annotation e.g. `cq:deprecated` property
40
41
3.`INTERNAL_DEPRECATED`, same restrictions as `INTERNAL` but due to being marked as deprecated in some external sources like release notes
41
42
4.`FINAL`
42
43
5.`ABSTRACT`
43
-
6.`PUBLIC`
44
+
6.`PUBLIC`
44
45
45
-
(in order from most restricted to least restricted).
46
+
(in order from most restricted to least restricted).
46
47
The explanation for those can be found in the [Adobe documentation][1].
47
48
The CSV format is based on [RFC 4180][7]. In addition a comment starting with `#` on the first line is supposed to contain a label for the map (like the underlying AEM version). `path` is supposed to be an absolute JCR path of a specific node.
48
49
@@ -94,8 +95,8 @@ There are several reasons:
94
95
95
96
1. You should detect violations as early as possible, preferably already in your CI pipeline. The later you detect those the more effort it is to fix.
96
97
2. If you don't care about content classifications
97
-
1. there is a high chance that you cannot easily upgrade to a newer AEM version (AMS or on-premise)
98
-
2. it might break with every new [AEM as a Cloud Service][5] release
98
+
1. there is a high chance that you cannot easily upgrade to a newer AEM version (AMS or on-premise)
99
+
2. it might break with every new [AEM as a Cloud Service][5] release
Copy file name to clipboardExpand all lines: aem-classification-validator/src/main/java/biz/netcentric/filevault/validator/aem/classification/AemClassificationValidator.java
Copy file name to clipboardExpand all lines: aem-classification-validator/src/main/java/biz/netcentric/filevault/validator/aem/classification/AemClassificationValidatorFactory.java
+27-12Lines changed: 27 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,9 @@ public class AemClassificationValidatorFactory implements ValidatorFactory {
0 commit comments