[jira] [Resolved] (SLING-7227) Repo Init: Add ability to register custom privileges

["Karl Pauls (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-7227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved SLING-7227.
-------------------------------
    Resolution: Fixed

[~bdelacretaz], I added the examples and merged the PR's. 

> Repo Init: Add ability to register custom privileges
> ----------------------------------------------------
>
>                 Key: SLING-7227
>                 URL: https://issues.apache.org/jira/browse/SLING-7227
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repoinit
>            Reporter: angela
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: Repoinit Parser 1.2.2, Repoinit JCR 1.1.8
>
>
> [~marett], [~bdelacretaz], looking at the repo-init source I couldn't find a way to register a custom privilege during repo init. I am sure this is an oversight and hasn't been omitted intentionally.
> The corresponding API calls are:
> {code}
> JackrabbitWorkspace.getPrivilegeManager()
> PrivilegeManager.registerPrivilege(String privilegeName, boolean isAbstract, String[] declaredAggregateNames)
> {code}
> See also
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/JackrabbitWorkspace.java?view=markup
> http://svn.apache.org/viewvc/jackrabbit/trunk/jackrabbit-api/src/main/java/org/apache/jackrabbit/api/security/authorization/PrivilegeManager.java?view=markup
> I would be appreciate if the repo init could have this gap filled. Thanks.



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