Robert Munteanu created SLING-3116: -------------------------------------- Summary: Node structures serialized to a .content.xml file do not propagate deletions Key: SLING-3116 URL: https://issues.apache.org/jira/browse/SLING-3116 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0
Assume that a .content.xml file like the one below changes by - removing the parent-1 node OR - removing the child-1-2 node We need to persist these deletions into the repository. However, we need to be careful to propagate these only for full coverage nodes. {code} <?xml version="1.0" encoding="UTF-8"?> <jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:vlt="http://www.day.com/jcr/vault/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:mixinTypes="[vlt:FullCoverage]" jcr:primaryType="sling:Folder" jcr:title="Full coverage parent"> <parent-1 jcr:primaryType="sling:Folder" jcr:title="Parent 1"> <child-1-1 jcr:primaryType="sling:Folder" jcr:title="Child 1-1"/> <child-1-2 jcr:primaryType="sling:Folder" jcr:title="Child 1-2"/> </parent-1> <parent-2 jcr:primaryType="sling:Folder" jcr:title="Parent 2"> <child-2-1 jcr:primaryType="sling:Folder" jcr:title="Child 2-1"/> <child-2-2 jcr:primaryType="sling:Folder" jcr:title="Child 2-2"/> </parent-2> </jcr:root> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira