Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 58526 invoked from network); 9 Nov 2001 00:33:35 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Nov 2001 00:33:35 -0000 Received: (qmail 9078 invoked by uid 97); 8 Nov 2001 13:40:29 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 9046 invoked by uid 97); 8 Nov 2001 13:40:29 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 8990 invoked from network); 8 Nov 2001 13:40:28 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: [PATCH] Asynchronous execution of processes References: <005b01c1678c$455475d0$0100a8c0@jose> From: Stefan Bodewig Date: 08 Nov 2001 14:36:33 +0100 In-Reply-To: "Jose Alberto Fernandez"'s message of "Wed, 7 Nov 2001 13:01:03 -0000" Message-ID: Lines: 27 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.4 (Civil Service) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 7 Nov 2001, Jose Alberto Fernandez wrote: > Here I am again, OH NO!!! :-) scary ;-) > The changes do not rely on any OS specifics (all Java) and you can > still use the timeout option to stop the forked process (as long as > ANT's VM is still running). I'm not sure whether this satisfies all use cases people have for detach, leaving the currently running VM completely would probably be preferred by most people. Maybe we should use your version for all the OSes we don't have an OS dependent version for? The Unix case would be more or less trivial as long as detach="true" implies running via a shell script. A platform dependent solution would make the use of a timeout feature impossible, but I don't think a combination of detach (which is spawn and forget about it in my book) and timeout is something people will need anyway. Why does detach imply fork for using your implementation? You could as well wrap a daemon thread around invoking the classes main as well. Stefan -- To unsubscribe, e-mail: For additional commands, e-mail: