jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-442) Implement a backup tool
Date Tue, 19 May 2009 10:33:45 GMT

     [ https://issues.apache.org/jira/browse/JCR-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-442:
------------------------------

      Component/s: jackrabbit-standalone
                   jackrabbit-core
    Fix Version/s: 1.6.0
         Assignee: Jukka Zitting

I'm taking over this issue to implement the repository backup and migration tool we need to
have in Jackrabbit 1.6 so we can better handle upgrades to the upcoming Jackrabbit 2.0 release.

> 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.


Mime
View raw message