You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Paco Avila (JIRA)" <ji...@apache.org> on 2009/02/09 14:10:59 UTC
[jira] Issue Comment Edited: (JCR-1972) Preserving UUID and
document version history on repository migration
[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671842#action_12671842 ]
monkiki edited comment on JCR-1972 at 2/9/09 5:10 AM:
---------------------------------------------------------
Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1.4.6 and i'm not sure if it works for more recent versions.
was (Author: monkiki):
Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1.4.6
> Preserving UUID and document version history on repository migration
> --------------------------------------------------------------------
>
> Key: JCR-1972
> URL: https://issues.apache.org/jira/browse/JCR-1972
> Project: Jackrabbit Content Repository
> Issue Type: Wish
> Components: jackrabbit-core
> Affects Versions: core 1.4.8
> Reporter: Paco Avila
> Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch
>
>
> I have been working I an migration utility for OpenKM and I performed some changes in jackrabit-core to enable version import, preserving
> the modification date. Also modified org.apache.jackrabbit.core.NodeImpl to preserve UUID in the migration process.
> This migration process is needed because there are changes in repository node definition, and Jackrabbit can't deal with this actually.
> I've attache a PDF with the changes needed in Jackrabbit-core. It works and there was no problems with the migrated repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.