[jira] [Commented] (SLING-11112) Regression in content loader : Diffent behaviour when initial content is missing

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus commented on SLING-11112:
-----------------------------------------

To me the behaviour is reasonable and in sync with the documentation at https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#initial-content-loading.
What other behaviour should one expect for such cases?

If the library in former versions has not overwritten {{/libs/foo/bar}} although specified via directives I would rather say the former versions just had a bug in them.
Do we need to optionally re-enable that buggy behaviour with a flag? 

> Regression in content loader : Diffent behaviour when initial content is missing
> --------------------------------------------------------------------------------
>
>                 Key: SLING-11112
>                 URL: https://issues.apache.org/jira/browse/SLING-11112
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: JCR ContentLoader 2.5.0
>            Reporter: Carsten Ziegeler
>            Priority: Blocker
>             Fix For: JCR ContentLoader 2.5.2
>
>
> With a bundle that does not have SLING-INF and the following initial content instruction:
> SLING-INF/content;path:=/libs/foo/bar;overwrite:=true;
> it seems that prior versions handled this case differently and did not touch /libs/foo/bar while the new behaviour removes all child nodes of /libs/foo/bar



--
This message was sent by Atlassian Jira
(v8.20.1#820001)