jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JCR-2653) Don't let a restore to base version create a new version with simple versioning
Date Mon, 14 Jun 2010 12:20:13 GMT

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

Tobias Bocanegra reassigned JCR-2653:
-------------------------------------

    Assignee: Tobias Bocanegra

> Don't let a restore to base version create a new version with simple versioning
> -------------------------------------------------------------------------------
>
>                 Key: JCR-2653
>                 URL: https://issues.apache.org/jira/browse/JCR-2653
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: JCR 2.0
>    Affects Versions: 2.0.0
>            Reporter: Dieter Wachters
>            Assignee: Tobias Bocanegra
>
> I am using simple versioning and I want to have a 'cancel checkout' functionality.
> When using the restore functionality of the VersionManager to do this, a new version
is created every time.
> Quote from mailinglist (Tobias Bocanegra):
> mainly:
> 15.7.1 Simple vs. Full Versioning Before Restore Under simple versioning, if N is checked-in
then it is automatically checked-out before the restore is performed.
> ....
> 15.7.7 Simple vs. Full Versioning after Restore Under simple versioning N is automatically
checked-in.
> ...
> But i can see the need for a 'cancel checkout' also for simple versioning. maybe jsr283
is not too clear about that, but IMO a restore to the base version should not create a new
version for simple versioning, neither. because it makes no sense.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message