kwin commented on PR #44: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/44#issuecomment-1772778419
For me repoinit is not an imperative language but rather a descriptive one of a certain state. Compare with https://sling.apache.org/documentation/bundles/repository-initialization.html > The code (in form of statements) being executed through repoinit ensures that the repository has a certain state. In case the repository cannot be set up as being mandated through the repoinit statements the startup of the repository fails. This may happen in case the existing parent nodes have node type restrictions which don't allow for the new repository state or in general when the existing node/property state is conflicting with the target one. Therefore the example of first creating and then deleting a group is something which IMHO should no be supported by repoinit. Rather one should allow to set unbound ACLs in the first place (see SLING-12115). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
