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 2018/01/16 10:22:00 UTC

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

    [ https://issues.apache.org/jira/browse/SLING-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326965#comment-16326965 ] 

Robert Munteanu commented on SLING-6453:
----------------------------------------

[~kwin] - I think this has caused a regression, can you please take a quick look at SLING-7385?

> In case no filter.xml could be found nothing should be synchronized
> -------------------------------------------------------------------
>
>                 Key: SLING-6453
>                 URL: https://issues.apache.org/jira/browse/SLING-6453
>             Project: Sling
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.1.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)