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 [EMAIL PROTECTED]
We are what we pretend to be
msg17957/pgp00000.pgp
Description: PGP signature
