[
https://issues.apache.org/jira/browse/JCR-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-442.
-------------------------------
Resolution: Fixed
The RepositoryCopier tool in jackrabbit-core and the backup options in
jackrabbit-standalone now provide a simple mechanism for backing up or
migrating repositories. Resolving as fixed for 1.6.0!
> Implement a backup tool
> -----------------------
>
> Key: JCR-442
> URL: https://issues.apache.org/jira/browse/JCR-442
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-core, jackrabbit-standalone
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 1.6.0
>
> Attachments: backup-final2.tar.gz, backupTool-final1.tar.gz,
> 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-jr-final1.tar.gz, 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.
-
You can reply to this email to add a comment to the issue online.
