[
https://issues.apache.org/jira/browse/SLING-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176769#comment-14176769
]
Robert Munteanu edited comment on SLING-4069 at 10/20/14 9:52 AM:
------------------------------------------------------------------
After discussing with [~justinedelson], our behaviour should mirror that
FileVault does, that is
{quote}creates necessary intermediate parent nodes if they don't exist even if
they
aren't in the filter. It will actually use the .content.xml files in the
package to populate those nodes, but again only if they don't exist.{quote}
We can probably add optional flags to the AddOrUpdateNodeCommand to handle this
situation, e.g. {{OperationFlag.CREATE_ONLY_IF_MISSING}} .
was (Author: rombert):
After discussing with [~justinedelson], our behaviour should mirror
> Intermediate resources that do not match the filter are not created when
> publishing
> -----------------------------------------------------------------------------------
>
> Key: SLING-4069
> URL: https://issues.apache.org/jira/browse/SLING-4069
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.4
> Reporter: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.6
>
>
> With SLING-3586 being fixed, when creating parent resources for published
> nodes we ensure that parent resources are created. However, we only take into
> account parent nodes which are matches by the workspace filter.
> Apparently FileVault ensures that these intermediate nodes are created
> anyway, so we should look into emulating that behaviour.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
