jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Unico Hommes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3507) Make it possible to remove version histories via the internal version management API
Date Fri, 08 Feb 2013 11:29:13 GMT

    [ https://issues.apache.org/jira/browse/JCR-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574405#comment-13574405
] 

Unico Hommes commented on JCR-3507:
-----------------------------------

Looking more closely after a test fell over, it doesn't seem trivial to add a separate permission.
Perhaps use Permission#VERSION_MNGMT after all. Or else a good old system property?
                
> 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

Mime
View raw message