Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 99465 invoked from network); 26 Nov 2001 18:04:17 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 26 Nov 2001 18:04:17 -0000 Received: (qmail 22097 invoked by uid 97); 26 Nov 2001 18:03:59 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 22062 invoked by uid 97); 26 Nov 2001 18:03:58 -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 22026 invoked from network); 26 Nov 2001 18:03:58 -0000 Message-ID: From: thomas.cherel@ascentialsoftware.com To: ant-dev@jakarta.apache.org Cc: thomas.cherel@ascentialsoftware.com Subject: append and timeout to the Java task Date: Mon, 26 Nov 2001 13:06:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Some modification propositions to the Java task. What do you guys think? Add append attribute, so the output is append to the output file when specified. Add timeout attribute to kill the java program if taking too long (only when fork is enabled). Some of those needs came from some build.xml that I am creating to do unit/integration testing. For append, I realized that I can avoid doing that by using a recorder and not specifying any output, but I think it will be a nice to have. Actually, the output/append/record type of things should probably be generalized. I saw a couple of things going this way that I need to look at closer to understand better. Thomas -- To unsubscribe, e-mail: For additional commands, e-mail: