[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574418#comment-13574418
]
angela commented on JCR-3507:
-----------------------------
unico... sorry for the delay.
i think using the version-mgt permission for that was fine... not sure if
inventing a separate permission is worth the effort
and really meaningful. with respect to the question whether the permission
should be present on the repository level
or if having permission on the versionhistory was sufficient, i would prefer
the check on the versionhistory as it
adds more flexibility to enforce the permission (in particular if we consider
JCR-3492). in contrast, when using a
repository-level permission you can just turn it on or off in globo for a given
principal.
> Make it possible to remove version histories via the internal version
> management API
> ------------------------------------------------------------------------------------
>
> Key: JCR-3507
> URL: https://issues.apache.org/jira/browse/JCR-3507
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, versioning
> Reporter: Unico Hommes
> Assignee: Unico Hommes
> Fix For: 2.7
>
>
> Version histories can become orphaned. This happens when the subject node is
> removed from the repository. In order to deal with the problem of
> indefinitely growing data stores, it should be possible to create
> functionality that removes such orphaned version histories.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
