[jira] Updated: (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 ] Paco Avila updated JCR-1972: Attachment: Jackrabbit_modifications.pdf This PDF shows the modifications needed in the jackrabbit core to preserve node UUID and document version history date in repository migrations. > 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 > > > 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.
[jira] Updated: (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 ] Paco Avila updated JCR-1972: Attachment: JCR-1972.patch 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.
[jira] Updated: (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: --- Status: Patch Available (was: Open) > 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.
[jira] Updated: (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: --- Status: Open (was: Patch Available) If I read the patch correctly, it breaks the NodeImpl.checkin() method. Also, please use only spaces (no tabs) for indentation. Other than that I think the changes are reasonable. We may even want to consider adding the extra method signatures to jackrabbit-api. > 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.
[jira] Updated: (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 ] Paco Avila updated JCR-1972: Attachment: JCR-1972_1.x.patch Updated patch for the 1.x branch > 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.
[jira] Updated: (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 ] Paco Avila updated JCR-1972: Comment: was deleted (was: In 1.x branch, the class org.apache.jackrabbit.core.NodeImpl.java is this: public synchronized NodeImpl addNode(Name nodeName, Name nodeTypeName, UUID uuid) So, it already accept an UUID parameter for new node creation.) > 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.
[jira] Updated: (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 ] 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.
[jira] Updated: (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 ] Paco Avila updated JCR-1972: Attachment: JCR-1972_1.x.patch Improvements by recommendation of Jukka > 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 > > > 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.
[jira] Updated: (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.
[jira] Updated: (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 ] 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.