[ http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12423466 ] Nicolas Toper commented on JCR-442: -----------------------------------
A few remarks I forgot to write: I was outside of Internet connection for a few days, this is why this patch is so "big". You will find the current backup structure. Not everything is working and is final yet. Some code still needs refactoring and to be commented. Can you please tell me which test case should I write? Do you have any idea already? Can you please check the way I am doing the backup is fine. Soon, we will be able to backup things up :) > Implement a backup tool > ----------------------- > > Key: JCR-442 > URL: http://issues.apache.org/jira/browse/JCR-442 > Project: Jackrabbit > Issue Type: New Feature > Reporter: Jukka Zitting > Attachments: jackrabbit-1.patch.txt, patch, patch-backup-060716.txt, > patch-backup-060719.txt, patch-backup-060725.txt, > patch-jackrabbit-060716.txt, patch-jackrabbit-060718.txt, > patch-jackrabbit-060725.txt, patch.txt, patch.txt, patch.txt, patch.txt > > > Issue for tracking the progress of the Google Summer of Code project assigned > to Nicolas Toper. The original project requirements are: > "Implement a tool for backing up and restoring content in an Apache > Jackrabbit content repository. In addition to the basic content hierarchies, > the tool should be able to efficiently manage binary content, node version > histories, custom node types, and namespace mappings. Incremental or > selective backups would be a nice addition, but not strictly necessary." -- 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
