[
https://issues.apache.org/jira/browse/SLING-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643384#comment-17643384
]
Angela Schreiber commented on SLING-11467:
------------------------------------------
if this improvement is adopted i would suggest to use a similar solution than
exists for user/group creation that allows to make sure the specified
intermediate path is really used (and not ignored if the user/group already
exists) with a 'forced' key word (see
https://github.com/apache/sling-org-apache-sling-repoinit-parser/blob/master/src/main/javacc/RepoInitGrammar.jjt#L103).
> support to update existing paths via repoinit statement
> -------------------------------------------------------
>
> Key: SLING-11467
> URL: https://issues.apache.org/jira/browse/SLING-11467
> Project: Sling
> Issue Type: Improvement
> Components: Repoinit
> Reporter: Darshan Mahor
> Priority: Major
>
> As of now we can't update the path if it already exists in repository[1] via
> repoinit statements like update primary type etc. This request is to support
> the mechanism via which we can modify/update the existing paths with the
> update/modification provided in repoinit statement. e.g. lets suppose we have
> a path in repostiory /content/test/testchild(nt:folder) and we want to
> modify it to /content/test/testchild(sling:Folder).
>
> [1].
> [https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/master/src/main/java/org/apache/sling/jcr/repoinit/impl/AclVisitor.java#L189]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
