Re: Creating the tmp directory if it doesn't exist

[Nicolas]

One issue is the size of the tmp directory.

During backup, I first write here all workspaces (one at a time) and the
version history. This is why I included a parameter to set it up since you
might want to sett it up on another disk.

I propose to keep the parameter and if it is not set (this would be the
default configuration), I will simply use the current directory (I put there
only one file, delete it, then another file and so on).

What do you think?

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

I think it's better to automatically create such a working directory

if it doesn't exist. It simplifies deployment and doesn't really hurt
anyone.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development

Re: Creating the tmp directory if it doesn't exist

[Jukka Zitting]

Hi,

On 7/28/06, Nicolas <[EMAIL PROTECTED]> wrote:

The backup code is using a tmp directory configured in the XML conf file. If
the directory doesn't exist, the code throws an exception. It seems the
right behaviour to me. But if you'd prefer, I can create the directory
and/or reset it.


I think it's better to automatically create such a working directory
if it doesn't exist. It simplifies deployment and doesn't really hurt
anyone.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [EMAIL PROTECTED]
Software craftsmanship, JCR consulting, and Java development