Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of michael.neale@gmail.com
 designates 64.233.184.231 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=Vqa8e7HBSJriGm+d4TATAgKcEz6z08fOxosnPmcHzNB92kMkYGJ2/bvcUli9vhUKdBVCXijMiuHEWDzzZMd2pdVggFaTKcRUeE8f/k2J4UeNtn7tEmCPPmkHfhIb9rM0YlhtL3K4h7K0utWiwEYAlL++ePBX54/GWaAbGuAUeQY=
Message-ID: <96ab3ced0611280314j29e7f8c7y642b32f616c1334d@mail.gmail.com>
Date: Tue, 28 Nov 2006 11:14:40 +0000
From: "Michael Neale" <michael.neale@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Backup tool for Jackrabbit
In-Reply-To: <fcbb46050611280301p9b4ca64j2671e18282911b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_8592_9195390.1164712480598"
References: <96ab3ced0611280214v26b834a5o5f1469f0c5e05fc0@mail.gmail.com>
	 <fcbb46050611280301p9b4ca64j2671e18282911b@mail.gmail.com>

------=_Part_8592_9195390.1164712480598
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Thanks Nicolas.

I am very interested in being able to use this for migration of data to a
new version of a repository - I think its a critical feature, suprised no
one has asked for it yet ! So I would encourage you to look into it !

So what needs to be done to add in this feature?

Michael.

On 11/28/06, Nicolas <ntoper@gmail.com> wrote:
>
> Hi Michael,
>
> On 11/28/06, Michael Neale < michael.neale@gmail.com> wrote:
> >
> > Can anyone tell me what the status is of the backup tool for jackrabbit?
> I
> > remember reading that it was functional - is it now (1.1) part of the
> > jackrabbit distro? (I have the wiki page on it, that is all).
>
>
> It is part in the contrib directory.
>
> There are still some parts uncommitted (but in JIRA) so please don't use
> it.
> I am taking this opportunity to rethink the design of a few classes and
> perform some house cleaning tasks (add good unit test, some class
> renaming,...). I should post on JIRA a new zip by the end of this week or
> the next one.
>
> As I am not a committer, I don't know when the commit will actually be
> performed, but based on off ML discussion I am pretty confident it should
> be
> quite fast after I post the code.
>
> I am also interested in if the backup/restore tool is suitable for the
> > following scenarios:
> >
> > 1) migrating from one repository with data to an new empty repository.
>
>
> It is built for this.
>
> 2) exporting from one version of the repository, and loading into a newer
> > version of the repository (with node types, but no data) (perhaps with
> new
> > node types) - basically seeing if it can be used for migrtion of data
> for
> > repo changes over time. This is a real worry of mine, I still don't
> > understand how I can make my repository cope with Version 2.0 of the
> > application when there is existing data ??? any ideas?
>
>
> We discussed this use case. It is not currently supported, but I designed
> the project in a way where it is quite easy to support it. If you give me
> a
> few more weeks, I can add it quite easily.
>
> This new feature can be added in an afternoon (I know I have hardly free
> time those days). All contributions on this are welcome :)
>
> BR,
> Nico
> my blog! http://www.deviant-abstraction.net !!
>
>

------=_Part_8592_9195390.1164712480598--