[jira] Created: (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:all-tabpanel ]

Jukka Zitting updated JCR-1972:
-------------------------------

    Attachment: JCR-1972_1.x.patch

Thanks! I made some modifications to the patch (no tabs, less extra methods, even less code duplication; see attached patch for details) and committed it to the 1.x branch in revision 800385.

I'll see what it takes to forward port this to the trunk.

> 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
>            Assignee: Jukka Zitting
>         Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.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.

    [ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738363#action_12738363 ]

Jukka Zitting commented on JCR-1972:
------------------------------------

One more thing... Your patch referenced a CheckinCalendarTest class, but the relevant java file wasn't included in the patch. Can you attach the file so we can include it in the test suite?

> 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
>            Assignee: Jukka Zitting
>         Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.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.

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

Jukka Zitting resolved JCR-1972.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

The new method signatures are now available also in trunk. Resolving as fixed for 1.6.0.

> 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
>            Assignee: Jukka Zitting
>             Fix For: 1.6.0
>
>         Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.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.

    [ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738544#action_12738544 ]

Paco Avila commented on JCR-1972:
---------------------------------

Sorry for the missing test class. I did no review of the generated patch and thought it was included. I'm on holiday but i will try to get a decent Internet connection to attach the missing class.

> 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
>            Assignee: Jukka Zitting
>             Fix For: 1.6.0
>
>         Attachments: Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.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.

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

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

    Attachment: CheckinCalendarTest.java

The missing test class

> 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
>            Assignee: Jukka Zitting
>             Fix For: 1.6.0
>
>         Attachments: CheckinCalendarTest.java, Jackrabbit_modifications.pdf, JCR-1972.patch, JCR-1972_1.x.patch, JCR-1972_1.x.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.