Hi, 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? Regards, Marcelo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
