If you download Process Explorer from www.sysinternals.com you can do a
search for the file, and see which process has a handle on it. Make sure
you are viewing handles and not DLLs first.
jamie
> -----Original Message-----
> From: conor [mailto:[EMAIL PROTECTED]]
> Sent: 18 August 2001 01:41
> To: ant-user; mhudson
> Cc: conor
> Subject: Re: Deleting a Jar in ant.
>
>
> From: "Michael J. Hudson" <[EMAIL PROTECTED]>
> >
> > Since I had seen an earlier bug kind of like this one...
> I'm thinking
> > that ANT may have a couple of FileStreams that the code creates and
> > still has handles to...
> >
> > In any case... in my ANT build.xml file... I compile all
> of my class
> > files, and JAR them up... however, I delete my previous
> copy of the JAR
> > before I JAR them up. For some reason, ANT can't delete it because
> > it's still being used somehow. I'm on a Windows NT
> machine... and this
> > actually works fine on a Linux-box. I had the same kind of issue a
> > couple of weeks ago with some output from a XALAN process that ANT
> > created. Same platform difference as well. And we found out that
> > this previous bug was a problem with ANT's TraxLiaison file.
> >
> > So... I'm pretty sure there must be something similar wrong in this
> > case, but not quite sure what it might be. Any ideas? Is
> it possible
> > that the last time I ran ANT, that the resouce handle to the JAR
> > file that was last created is still being used?
>
> No, but if the jar is in your classpath the JVM itself will
> have a lock on
> it, I believe. Is that the case here?
>
> Conor
>
>
>
>
>
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
