ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcelo Nery dos Santos <>
Subject java task: fork vs spawn
Date Fri, 29 Jul 2005 04:36:34 GMT

The fork option (to the java task) is creating a java process
outliving ant. Is it ok?


The specification of the "fork" option is:

if enabled triggers the class execution in another VM (disabled by default)

While the specification of the "spawn" states that:

if enabled allows to start a process which will outlive ant.
Requires fork=true


If I use a regular kill to finish the ant process, a clean-up happens
also killing the forked JVM. On the other hand, if a "kill -9" is
used, the forked VM remains dangling, detached from any ant process.

Is there a way to keep those processes tighten?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message