[jira] [Resolved] (JCRVLT-216) Aggregate defined children of the filter path ancestors, optionally install them

["Tobias Bocanegra (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCRVLT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tobias Bocanegra resolved JCRVLT-216.
-------------------------------------
    Resolution: Won't Fix

> Aggregate defined children of the filter path ancestors, optionally install them
> --------------------------------------------------------------------------------
>
>                 Key: JCRVLT-216
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-216
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Nicolas Peltier
>
> When a package is defined with a filter /content/foo/bar and foo has in its nodetype children definition some expected node, would be nice to aggregate them, with some special flag
> At install time, if the flag is here and target content doesn't have the child, then install it.
> Use case in AEM is /content/foo/bar being a tree of pages we are interested in, and being able to build a package only with /content/foo/bar filter, not
> /content/foo/bar
> /content/foo/jcr:content
> when you know the problem it's relatively quick to workaround, when you don't it always waste some time debugging why all is broken because /content/foo doesn't have a content child.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)