Yeah, I refreshed my tree about an hour ago.
> From: David Jencks <[EMAIL PROTECTED]> > Date: Tue, 12 Feb 2002 19:33:42 -0500 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] [ jboss-Bugs-516707 ] Undeploy Broken on MacOS X > > Just to check... > > Are you guys seeing all these problems with last nights changes to > MainDeployer etc? > > thanks > david jencks > > On 2002.02.12 18:43:48 -0500 Jules Gosnell wrote: >> I'm seeing similar behaviour on Linux sun/1.3.1. >> >> 1. copying over the top of a jar in deploy/ doesn't seem to wake the >> deployer up. >> 2. sometimes the deployer just seems to stop working. >> >> I haven't said anything because I figured it was all still in a state of >> flux, but I >> thought Hunter could do with some backing up ! >> >> If I nail it down any further I will post. >> >> Jules >> >> >> [EMAIL PROTECTED] wrote: >> >>> Bugs item #516707, was opened at 2002-02-12 15:28 >>> You can respond by visiting: >>> http://sourceforge.net/tracker/?func=detail&atid=376685&aid=516707&group_id= >>> 22866 >>> >>> Category: JBossServer >>> Group: v3.0 Rabbit Hole >>> Status: Open >>> Resolution: None >>> Priority: 5 >>> Submitted By: Hunter Hillegas (hunterhillegas) >>> Assigned to: Nobody/Anonymous (nobody) >>> Summary: Undeploy Broken on MacOS X >>> >>> Initial Comment: >>> The new deployer doesn't seem to undeploy >>> reliably on MacOS X. >>> >>> When an ear is removed from the deploy directory, >>> nothing happens. >>> >>> This worked fine before the new deployer was >>> implemented so I don't think it is a MacOS X JVM >>> bug. >>> >>> Even if it is, Apple probably won't fix it unless we >>> can tell them where the bug is. >>> >>> ---------------------------------------------------------------------- >>> >>>> Comment By: Hunter Hillegas (hunterhillegas) >>> Date: 2002-02-12 15:33 >>> >>> Message: >>> Logged In: YES >>> user_id=7380 >>> >>> It looks like it is the same story for deploying new ears >>> placed in the directory after the server has started... >>> They are never noticed... Again, this worked fine before >>> the deployer re-write. >>> >>> ---------------------------------------------------------------------- >>> >>> You can respond by visiting: >>> http://sourceforge.net/tracker/?func=detail&atid=376685&aid=516707&group_id= >>> 22866 >>> >>> _______________________________________________ >>> Jboss-development mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/jboss-development >> >> <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> >> <html> >> I'm seeing similar behaviour on Linux sun/1.3.1. >> <p>1. copying over the top of a jar in deploy/ doesn't seem to wake the >> deployer up. >> <br>2. sometimes the deployer just seems to stop working. >> <p>I haven't said anything because I figured it was all still in a state >> of flux, but I thought Hunter could do with some backing up ! >> <p>If I nail it down any further I will post. >> <p>Jules >> <br> >> <p>[EMAIL PROTECTED] wrote: >> <blockquote TYPE=CITE>Bugs item #516707, was opened at 2002-02-12 15:28 >> <br>You can respond by visiting: >> <br><a >> href="http://sourceforge.net/tracker/?func=detail&atid=376685&aid=516707&grou >> p_id=22866">http://sourceforge.net/tracker/?func=detail&atid=376685&a >> id=516707&group_id=22866</a> >> <p>Category: JBossServer >> <br>Group: v3.0 Rabbit Hole >> <br>Status: Open >> <br>Resolution: None >> <br>Priority: 5 >> <br>Submitted By: Hunter Hillegas (hunterhillegas) >> <br>Assigned to: Nobody/Anonymous (nobody) >> <br>Summary: Undeploy Broken on MacOS X >> <p>Initial Comment: >> <br>The new deployer doesn't seem to undeploy >> <br>reliably on MacOS X. >> <p>When an ear is removed from the deploy directory, >> <br>nothing happens. >> <p>This worked fine before the new deployer was >> <br>implemented so I don't think it is a MacOS X JVM >> <br>bug. >> <p>Even if it is, Apple probably won't fix it unless we >> <br>can tell them where the bug is. >> <p>---------------------------------------------------------------------- >> <p>>Comment By: Hunter Hillegas (hunterhillegas) >> <br>Date: 2002-02-12 15:33 >> <p>Message: >> <br>Logged In: YES >> <br>user_id=7380 >> <p>It looks like it is the same story for deploying new ears >> <br>placed in the directory after the server has started... >> <br>They are never noticed... Again, this worked fine before >> <br>the deployer re-write. >> <p>---------------------------------------------------------------------- >> <p>You can respond by visiting: >> <br><a >> href="http://sourceforge.net/tracker/?func=detail&atid=376685&aid=516707&grou >> p_id=22866">http://sourceforge.net/tracker/?func=detail&atid=376685&a >> id=516707&group_id=22866</a> >> <p>_______________________________________________ >> <br>Jboss-development mailing list >> <br>[EMAIL PROTECTED] >> <br><a >> href="https://lists.sourceforge.net/lists/listinfo/jboss-development";>https:/ >> /lists.sourceforge.net/lists/listinfo/jboss-development</a></blockquote> >> </html> >> > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
