You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by kw...@apache.org on 2020/03/10 11:20:25 UTC
svn commit: r1875034 -
/jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md
Author: kwin
Date: Tue Mar 10 11:20:25 2020
New Revision: 1875034
URL: http://svn.apache.org/viewvc?rev=1875034&view=rev
Log:
JCRVLT-417 document new ancestor node handling
Modified:
jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md
Modified: jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md
URL: http://svn.apache.org/viewvc/jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md?rev=1875034&r1=1875033&r2=1875034&view=diff
==============================================================================
--- jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md (original)
+++ jackrabbit/commons/filevault/trunk/vault-doc/src/site/markdown/filter.md Tue Mar 10 11:20:25 2020
@@ -132,7 +132,7 @@ yes | no | no | not existing
All *uncovered* ancestor nodes are either
1. created with the node type and properties given in the package (in case the node type *is* given with a `.content.xml` at the right location and the node does not yet exist in the repo)
-1. created with node type `nt:folder` (in case they the node type is *not* given with a `.content.xml` at the right location and the node does not yet exist in the repo) or
+1. since version 3.4.4 ([JCRVLT-417](https://issues.apache.org/jira/browse/JCRVLT-417)) created with the ancestor node type's default child type or if that is not set or prior to version 3.4.4 created with node type `nt:folder` (in case the the node type is *not* given with a `.content.xml` at the right location and the node does not yet exist in the repo) or
1. not touched at all (in case they are already existing in the repo, no matter which node type is given with a `.content.xml` at the according location)
### Example