This requires a new file for cases that don't have a problem today. A better
solution is to allow one to lock a deployment jar by creating a my.ear.lock
that tells the deployer to ignore the my.ear until the lock is removed.
----- Original Message -----
From: "Jim Brownfield" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 15, 2001 8:51 AM
Subject: RE: autodeployer bug RE: [JBoss-dev] problems with latest
jboss-jetty?
> Would this still leave a problem for people deploying over modems (I do
this
> all the time)? What if deployment were triggered by an empty auxiliary
file
> named like the original file (something like my-ear.dpy for my.ear). Then
> you could ftp (or whatever) the file to the deploy directory and
immediately
> ftp the empty file afterwards. The deployer would be scanning for ".dpy"
> files.
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
