[SLING-6453] In case no filter.xml could be found nothing should be synchronized

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Sling Eclipse IDE 1.1.0
• Fix Version/s: Sling Eclipse IDE 1.2.0
• Component/s: IDE
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 11/Jan/17 15:25
• Updated: 21/Jan/18 20:23
• Resolved: 22/Jan/17 16:46

Description

In case a filter file is not found the method ResourceChangeCommandFactory#getFilterResult returns ALLOW while it should return DENY to not overwrite any nodes in case the filter rules could not be determined. Look at SLING-6344 for a concrete example where that behaviour lead to partly broken Sling servers.

That would affect synchronisation and dedicated import/export.

Issue Links

• relates to: SLING-6344 Support filter.xmls being generated by the content-package-maven-plugin