[
https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Unico Hommes resolved JCR-3507.
-------------------------------
Resolution: Fixed
Alright. That is indeed what I now did for deleting version history objects: do
a check for version management permission on the version history instead of on
the repository level. Thank you for you feedback. I will close the issue.
> 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
