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

Stefan Egli updated SLING-3741:
-------------------------------
    Description: 
Minimal scenario reported by [~stefanegli]

* Create:
{code}
grandparent [nt:unstructured]
\- parent [nt:unstructured]
 |- child1 [nt:unstructured]
 \- child2 [nt:unstructured]
{code}
* Then change child2 to sling:Folder
* Changing child2 back to nt:unstructured then causes the deletion of parent 
(since I delete parent/child2 and parent folders explicitly, as they are no 
longer needed)


  was:
Minimal scenario reported by [~egli]

* Create:
{code}
grandparent [nt:unstructured]
\- parent [nt:unstructured]
 |- child1 [nt:unstructured]
 \- child2 [nt:unstructured]
{code}
* Then change child2 to sling:Folder
* Changing child2 back to nt:unstructured then causes the deletion of parent 
(since I delete parent/child2 and parent folders explicitly, as they are no 
longer needed)



> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -------------------------------------------------------------------------------------------------
>
>                 Key: SLING-3741
>                 URL: https://issues.apache.org/jira/browse/SLING-3741
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.0.2
>
>         Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~stefanegli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to