You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/05/26 13:42:01 UTC
[jira] [Commented] (SLING-3586) Publishing content fails if
intermediate nodes are not present in the repository
[ https://issues.apache.org/jira/browse/SLING-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008772#comment-14008772 ]
Robert Munteanu commented on SLING-3586:
----------------------------------------
Given that
* I don't think this is a very frequent use case
* There is a workaround ( manually adjust the nodes in the repo )
I'm going to move this to 1.0.2 and see how many people complain.
> Publishing content fails if intermediate nodes are not present in the repository
> --------------------------------------------------------------------------------
>
> Key: SLING-3586
> URL: https://issues.apache.org/jira/browse/SLING-3586
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Consider the following scenario:
> - the repository contains /content (sling:Folder)
> - the local workspace contains /content/test/folder (sling:Folder )
> If I try to update a property on /content/test/folder, it fails because the parent folder /content/test is not present. We should fall back on retrieving the information about intermediate parent nodes and using that to create them if needed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)