[ http://issues.apache.org/jira/browse/JCR-442?page=all ]
Nicolas Toper updated JCR-442:
------------------------------
Attachment: patch-backup-090806.txt
Hopefully, this is one of the last patches for this project :)
Everything is working but the importXML method in the VersionManager hasn't
been finished yet (so not committed to core) so the node version history
restore is not working (and actually raises an exception since it looks for
it). If you need the tool already, please deactivate the node version history
restore for now.
The code still needs clean up and documentation but the meat of this contrib
project is here.
ETA: Monday.
Next steps: finish the importXML method (currently), clean up (trailing spaces
mostly), document (readme, wiki page), test + bug patches and requirements for
a version 2.
Some ideas have already been put for a V2 on the wiki page. I plan to start
working on it after Google SoC and when we would have gathered enough users
feedback. Please feel free to already put your ideas for a v2 and of course,
soon, please test the backup/restore.
> 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-060808-backup.txt,
> patch-backup-060716.txt, patch-backup-060719.txt, patch-backup-060725.txt,
> patch-backup-060726.txt, patch-backup-060728.txt, patch-backup-060803.txt,
> patch-backup-090806.txt, patch-jackrabbit-060716.txt,
> patch-jackrabbit-060718.txt, patch-jackrabbit-060725.txt,
> patch-jackrabbit-060726.txt, patch-jackrabbit-060728.txt,
> patch-jr-060803.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
