[
https://issues.apache.org/jira/browse/SLING-9090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282281#comment-17282281
]
Angela Schreiber edited comment on SLING-9090 at 2/10/21, 7:39 AM:
-------------------------------------------------------------------
[~Henry Kuijpers], i am not in charge of the sling repo-init tool, but i
considered this a major issue when i reported it.... not sure why it hasn't
been addressed. [~bdelacretaz], could you provide an ETA for this given the
fact that i already provided a patch back on March 29th 2020?
btw: the issue has been first reported in 2017 (see SLING-7147). adjusted the
'affects versions' accordingly.
cc: [~rombert], [~karlpauls]
was (Author: anchela):
[~Henry Kuijpers], i am not in charge of the sling repo-init tool, but i
considered this a major issue when i reported it.... not sure why it hasn't
been addressed. [~bdelacretaz], could you provide an ETA for this given the
fact that i already provided a patch back on March 29th 2020?
cc: [~rombert], [~karlpauls]
> AclLine.Action.REMOVE and AclLine.Action.REMOVE_ALL not handled in jcr
> implementation
> -------------------------------------------------------------------------------------
>
> Key: SLING-9090
> URL: https://issues.apache.org/jira/browse/SLING-9090
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.6, Repoinit JCR 1.1.8, Repoinit JCR
> 1.1.10, Repoinit JCR 1.1.12, Repoinit JCR 1.1.14, Repoinit JCR 1.1.16,
> Repoinit JCR 1.1.18, Repoinit JCR 1.1.20, Repoinit JCR 1.1.22, Repoinit JCR
> 1.1.24, Repoinit JCR 1.1.26
> Reporter: Angela Schreiber
> Priority: Major
>
> [~bdelacretaz], while the documentation and the parser code provides the
> ability to remove an individual or all access control entries, it seems the
> JCR implementation doesn't actually support it.
> using it may lead to odd side effects or failures.... so, i think either the
> parser should remove the support for Action.REMOVE and Action.REMOVE_ALL or
> the jcr implementation part should respect it... at the very minimum it
> should spot any usage of it and fail the repo-init if there is no way to
> implement it properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
