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] Commented: (JCR-442) Implement a backup tool
Date Tue, 18 Jul 2006 12:13:15 GMT
    [ http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12421854 ] 
Jukka Zitting commented on JCR-442:

> The new correct patch (I don't try to delete and recreate the same file within the same

I see what you're trying to do, but the patch still tries to modify the non-existent RepositoryConfigurationParser
class instead of correctly adding it. Did you start it as a copy of ConfigurationParser? I
tried doing the same and was able to apply the patch without problems.

Still, I didn't yet commit the change, as there are two issues I'd like resolved:

a) Make RepositoryConfigurationParser a subclass of ConfigurationParser and use inheritance
to access the protected methods from ConfigurationParser.
b) Remove the createSubParser() method from the ConfigurationParser base class, it's only
needed by RepositoryConfigurationParser.

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


View raw message