Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
Message-ID: <20010801144038.17794.qmail@uwdvg020.cms.usa.net>
Date: 1 Aug 01 08:40:38 MDT
From: Butch Clark <butch.clark@corp.usa.net>
To: ant-dev@jakarta.apache.org
Subject: Re: [Re: Windows Directory Locking]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


I'd be interested in seeing if anyone has a good solution to this issue. =
 We
have noticed that on Win2k the file locking can be a REAL problem.  There=
 have
been times we've copied files into the deployment directory that one of t=
he
servers is using, and when the server restarts, the original locked versi=
on
magically appears back where the new file used to be.  Unfortunately, I
haven't seen any consistency with exactly how this happens, or even when.=
=2E.

It's gotten to the point where we go to heroic lengths to _ensure_ that w=
hat
is deployed is exactly what we think is deployed.  I.e., shutting down th=
e
servers, deleting all the files, making sure they're _really_ not there,
redeploying the files, restarting the servers, etc.

Anyone else had these kinds of experiences (he asked, hoping it's not "ju=
st
me" :)

Butch

Ken Wood <kwood@i2.com> wrote:
> Welcome to life on the most popular
> toy operating system...
> =

> Alex Jeannopoulos wrote:
> > =

> > I haven't seen this on the list, so here is my question. Is there any=
 way
to
> > force ant to delete a directory even if it is open by another process=
=2E On
> > windows if I have explorer open to a directory which is to be deleted=
, and
I
> > launch my ant script it will fail since explorer holds a lock on
directory
> > and the build depends on the clean process. I have a feeling its an O=
S
> > feature but I figured maybe someone has an answer for it.
> > =

> > Alex Jeannopoulos


____________________________________________________________________
This email message is for the sole use of the intended recipient(s) and m=
ay contain confidential and privileged information. Any unauthorized revi=
ew, use, disclosure or distribution is prohibited. If you are not the int=
ended recipient, please contact the sender by reply email and destroy all=
 copies of the original message.