You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by ji...@apache.org on 2004/10/22 10:24:26 UTC
[jira] Resolved: (JCR-12) Clone version history
Message:
The following issue has been resolved as WON'T FIX.
Resolver: Tobias Strasser
Date: Fri, 22 Oct 2004 1:23 AM
for every mix:versionable node there exists a version history which is referenced by the jcr:versionHistory property of that node. internally, the version history is tied to that uuid of the versionable node. if you move the node within the workspace, or clone it to another workspace, the uuid of that node stays the same and so does the respective version history.
if you copy a node, it gets a new uuid, and therefore a new version history. it is not possible to copy the version history.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JCR-12
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JCR-12
Summary: Clone version history
Type: Wish
Status: Resolved
Priority: Minor
Resolution: WON'T FIX
Project: Jackrabbit
Components:
API
Assignee:
Reporter: Vadim L. Ivanov
Created: Wed, 20 Oct 2004 10:18 AM
Updated: Fri, 22 Oct 2004 1:23 AM
Environment: JCR
Description:
Whether there is any potential to copy/clone version history, for example, during repository "document" moving (by clone or somehow else) in node tree?
Or such operation is not consistent with JCR ideology?
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira