Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 79325 invoked from network); 2 Jul 2002 15:14:12 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Jul 2002 15:14:12 -0000 Received: (qmail 25387 invoked by uid 97); 2 Jul 2002 15:14:13 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 25347 invoked by uid 97); 2 Jul 2002 15:14:12 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 25335 invoked by uid 98); 2 Jul 2002 15:14:12 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <003501c221db$155f0b60$3f640a0a@sseal.secretseal.com> From: "Hal Hildebrand \(web\)" To: "Ant Users List" References: Subject: Re: Starting a Java application in the background. Date: Tue, 2 Jul 2002 08:13:27 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Is this under JDK 1.3 or 1.4? Ant 1.5 beta 2 fixed this to kill all spawned processes when the parent is terminated. Seems like the JDK did something different in their process spawning in JDK 1.3 that was different from previous versions. Spawned processes are not tied to the parent's lifetime in this version and above. ----- Original Message ----- From: "Ric Searle" > You are mixing up the children and parents relations of the two. A java > task is a child of the ant process. Killing the ant process will kill > its children as well. That's what I would have thought, but it doesn't. The java task that ant started carries on even when all of the ant processes have died. Ric On Monday, July 1, 2002, at 06:02 pm, Thomas Zander wrote: > You are mixing up the children and parents relations of the two. A java > task is a child of the ant process. Killing the ant process will kill > its children as well. > With the java process still living after ant died the children died and > the parent still lives. > > There is a way on linux to 'detach' a child from its parent. No idea if > Java supports that. > > So; like Steve said; its quite hard to write :) > > > from On Mon, Jul 01, 2002 at 11:41:01AM +0100, Ric Searle wrote: > > Thanks. It seems like a nice feature that ant could do with. > > > > I like the idea of saying to our support department, "Get version x.x > > from CVS, and then just type 'ant' to build and run it.". > > > > Here's a thought: Killing any of the ant processes (on Linux at > least) > > kills all of the ant processes, but leaves the Java task that ant > > started running. This is the effect I want, so is there a way of > getting > > ant to kill itself at the end of the build? > > > > Regards, > > > > Ric Searle > > > > > > On Friday, June 28, 2002, at 05:27 pm, Steve Loughran wrote: > > > > > > > > > > >>That's by design - usually java processes are part of the build, and > > >>the > > >build won't continue until the process has terminated. Ant will > > >redirect the > > >process's output/error streams to the build log, too. > > > > > >>It shouldn't be *too* hard to write some kind of "background" flag > in > > >>the > > >Java task, but I suspect you'd need to find >someone who truly > > >understands > > >that code first. > > > > > >There are some patche in bugzilla. > > > > > >It is hard to write, at least in a cross-platform way > > -- > Thomas Zander > zander@planescape.com > We are what we pretend > to be > -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: