[SLING-4098] Full coverage aggregates nested under a partial coverage aggregate incorrectly deleted when a sibling resource is published

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Sling Eclipse IDE 1.0.4
• Fix Version/s: Sling Eclipse IDE 1.0.6
• Component/s: IDE
• Assignee: Robert Munteanu
• Reporter: Robert Munteanu
• Created: 23/Oct/14 18:43
• Updated: 02/Mar/15 09:03
• Resolved: 24/Oct/14 22:39

Description

Consider the following content structure:

- item [sling:Folder]
\- config [sling:OsgiConfig]
\- html.jsp [nt:file]

When publishing a change on html.jsp, the config node is incorrectly deleted, as detected by the tracing code:

| Worker-14 | 2014-10-23 21:37:36.905 | org.apache.sling.ide.impl-vlt | /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | processDeletedNodes | 139 | Deleting node /apps/example/item/config as it is no longer present in the local
 checkout |

Other nt:file resources are not deleted when publishing. Also this does not happen unless the parent folder has a .content.xml file ; for an nt:folder parent the bug does not happen.