[ http://issues.apache.org/jira/browse/JCR-556?page=comments#action_12444079 ] Nicolas Toper commented on JCR-556: -----------------------------------
Hi, For those wondering, what is the status of the backup tool. It is working, but to make it really useful, Jukka and I are integrating it more closely to the core. We are also using this opportunity to fix a few issues. Please find here the list of the remaining tasks (some done and undone): - WorkspaceImporter refactoring (to avoid code duplicate): OK - Close JCR 535: waiting for commitment - new PropInfo: waiting for commitment (Flags inserted: see relevant JIRA issue) - BatchedItemOperations: waiting for commitment (Flags inserted: see relevant JIRA issue) - new set of test of the backup tool (to detect possible new issues and dependencies) - Add a raw parameter to the Importer (no postProcess node: no version history creation and so on) - setBatchedItemOperations: in WorkspaceImporter or in an inherited class? (used to import versioning) - versionManager: importVersions (can call a specific Importer if needed but find a way to get rid of the specific NodeVersionsHistoriesStateManager). We are nearly done :) I hope to close this project before the end of the month, if Jukka has enough time to review and integrate my patches. BR, Nico my blog! http://www.deviant-abstraction.net !! > Refactoring of the BackupTool > ----------------------------- > > Key: JCR-556 > URL: http://issues.apache.org/jira/browse/JCR-556 > Project: Jackrabbit > Issue Type: Improvement > Reporter: Nicolas Toper > Priority: Minor > Attachments: BIO.patch, patch-backup-040906.txt, > patch-jr-010906-NodeVersionHistoriesUpdatableStateManager.txt, > patch-jr-010906-PropInfo.txt, patch-jr-010906-RepositoryImpl.txt, > patch-jr-010906-SysViewImporter.txt, patch-jr-010906-VersionManagerImpl.txt, > PropInfo.patch > > > The BackupTool has still some refactoring to perform. I will propose the > patch on this new issue since we cannot change the JCR-442 (Google wants to > see a place where all the Google SoC work is). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
