[jackrabbit-filevault] branch master updated: releng: clarify type "cleanup"

[kw...@apache.org]

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

kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jackrabbit-filevault.git


The following commit(s) were added to refs/heads/master by this push:
     new f071d95e releng: clarify type "cleanup"
f071d95e is described below

commit f071d95e722afc4b08b15cea26e5dad8d172a0c5
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Wed Jun 29 14:37:08 2022 +0200

    releng: clarify type "cleanup"
---
 src/site/markdown/filter.md     | 3 ++-
 src/site/markdown/validation.md | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/src/site/markdown/filter.md b/src/site/markdown/filter.md
index 13b55b66..45adab5a 100644
--- a/src/site/markdown/filter.md
+++ b/src/site/markdown/filter.md
@@ -38,6 +38,7 @@ Example:
             <include pattern="/etc/project1/static(/.*)?" />
         </filter>
         <filter root="/etc/map" mode="merge" />
+        <filter root="/apps/old-project-location" type="cleanup" />
     </workspaceFilter>
 
 ### Filter Elements
@@ -52,7 +53,7 @@ importing content. the following values are possible:
 
 For a more detailed description of the import mode, see [here](importmode.html).
 
-In addition it is possible to influence the auto-detection of the package type (if not explicitly specified in the `properties.xml`) with the attribute `type`. The only supported value as of now is `cleanup` which means that the filter rule is ignored for the auto-detection of  the package type ([JCRVLT-220](https://issues.apache.org/jira/browse/JCRVLT-220))
+In addition it is possible to influence the auto-detection of the package type (if not explicitly specified in the `properties.xml`) with the attribute `type`. The only supported value as of now is `cleanup` which means that the filter rule is ignored for the auto-detection of the package type ([JCRVLT-220](https://issues.apache.org/jira/browse/JCRVLT-220)) as well as ignored for [validation of orphaned filter entries](validation.html) with the `jackrabbit-filter` validator. This is thou [...]
 
 
 ### Include and Exclude Elements
diff --git a/src/site/markdown/validation.md b/src/site/markdown/validation.md
index 86138c98..2b6fe43b 100644
--- a/src/site/markdown/validation.md
+++ b/src/site/markdown/validation.md
@@ -51,7 +51,7 @@ It is possible to run validation only on a subset of files contained in the pack
 
 ID  |  Description | Options | Incremental Execution Limitations
 --- | --- | --- | ---
-`jackrabbit-filter` |  Checks for validity of the [filter.xml](./filter.html) (according to a predefined  XML schema). In addition checks that every [docview xml node](./docview.html) is contained in the filter. It also makes sure that all filter root's ancestors are either known/valid roots or are contained in the package dependencies. For ancestor nodes which are not covered by a filter at least a `warn` is emitted. Also it makes sure that `pattern` values for includes/excludes as well [...]
+`jackrabbit-filter` | Checks for validity of the [filter.xml](./filter.html) (according to a predefined  XML schema). In addition checks that every [docview xml node](./docview.html) is contained in the filter. It also makes sure that all filter root's ancestors are either known/valid roots or are contained in the package dependencies. For ancestor nodes which are not covered by a filter at least a `warn` is emitted. Also it makes sure that `pattern` values for includes/excludes as well  [...]
 `jackrabbit-properties ` | Checks for validity of the  [properties.xml](./properties.html) | none | none
 `jackrabbit-dependencies` | Checks for overlapping filter roots of the referenced package dependencies as well as for valid package dependency references (i.e. references which can be resolved). | *severityForUnresolvedDependencies*: severity of validation messages for unresolved dependencies (default = `warn`) | none
 `jackrabbit-docviewparser` | Checks if all docview files in the package are compliant with the [(extended) Document View Format](docview.html). This involves checking for XML validity as well as checking for known property types and their valid string serializations. | *allowUndeclaredPrefixInFileName* (since 3.6.0): if set to `false` then prefixes only used in the encoded docview xml filename need to be declared as namespace in the XML itself, otherwise a missing namespace declaration i [...]