[
https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730372#action_12730372
]
Paco Avila commented on JCR-1972:
---------------------------------
I've updated the patch and also added two JUnit test (CheckinCalendarTest and
added a new method at NodeImplTest).
In addNode(..., UUID) I can test if the node has the MIX_REFERENCEABLE mixing
but I'm not sure if this good because the mixin can be added after the node
creation. This check is commented in the patch.
> 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
>
>
> 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.
