Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <21974381.1153003755770.JavaMail.jira@brutus>
Date: Sat, 15 Jul 2006 15:49:15 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-442) Implement a backup tool
In-Reply-To: <653998.1148469389882.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12421359 ] 
            
Jukka Zitting commented on JCR-442:
-----------------------------------

Applied the patches that removed the backup classes from core (patch.txt [12336377]) and added them to the contrib/backup subproject (patch.txt  [12336687]) .

The latter patch required some tweaking as it didn't compile out of the box (see BackupConfig.create(InputSource, String)). Please check that the project compiles before sending a patch, normally a patch that doesn't compile would be rejected without further consideration.  And (as already discussed in private) please also use spaces for indentation instead of tabs.

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