Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <686755409.1247735174883.JavaMail.jira@brutus>
Date: Thu, 16 Jul 2009 02:06:14 -0700 (PDT)
From: "Paco Avila (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1972) Preserving UUID and document version
 history on repository migration
In-Reply-To: <1244367136.1234171140307.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Paco Avila updated JCR-1972:
----------------------------

    Attachment: JCR-1972_1.x.patch

Check for existing UUID

> 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, JCR-1972_1.x.patch, JCR-1972_1.x.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.