jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas " <nto...@gmail.com>
Subject Re: [jira] Commented: (JCR-442) Implement a backup tool
Date Tue, 18 Jul 2006 22:05:30 GMT
Agreed. Sorry for the mess.  I don't think I'll have any move operations in
between. If I have some, I'll create the patch through the command line...

Nico

On 7/18/06, Jukka Zitting (JIRA) <jira@apache.org> wrote:
>
>     [
> http://issues.apache.org/jira/browse/JCR-442?page=comments#action_12421980]
>
> Jukka Zitting commented on JCR-442:
> -----------------------------------
>
> > Same issue as always for those patches: I delete and recreate the class.
> I don't know if it's solved but we won't have anymore this problem anyway
> for the next patches.
>
> Now it's even worse. This patch (patch-jackrabbit-060718.txt)  would
> totally remove the ConfigurationParser, and it still doesn't handle the
> RepositoryConfigurationParser class properly. I think I got your idea
> though, I'll recreate the changes manually to get us forward. It's perhaps
> better to avoid using the Eclipse file copy and move operations while
> working via patches.
>
> > 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-jackrabbit-060718.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
>
>
>


-- 
a+
Nico
my blog! http://www.deviant-abstraction.net !!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message