Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 22686 invoked from network); 10 Feb 2002 17:12:24 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Feb 2002 17:12:24 -0000 Received: (qmail 22084 invoked by uid 97); 10 Feb 2002 17:12:23 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 22036 invoked by uid 97); 10 Feb 2002 17:12:22 -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 22025 invoked from network); 10 Feb 2002 17:12:22 -0000 Message-ID: <3C66A8FD.668595CE@i2.com> Date: Sun, 10 Feb 2002 11:08:13 -0600 From: Ken Wood X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Ant Developers List Subject: Re: TryCatchFinallyTask ? References: <200202100929.g1A9TuE01804@mail016.syd.optusnet.com.au> <003201c1b226$09432020$d1eefea9@homenkf0y0hwu0> <200202101317.g1ADHG805938@mail008.syd.optusnet.com.au> <3C66784E.3010709@cortexebusiness.com.au> X-MIMETrack: Itemize by SMTP Server on i2HUB2/i2Tech(Release 5.0.8 |June 18, 2001) at 02/10/2002 11:12:17 AM, Serialize by Router on i2HUB2/i2Tech(Release 5.0.8 |June 18, 2001) at 02/10/2002 11:12:21 AM, Serialize complete at 02/10/2002 11:12:21 AM Content-Transfer-Encoding: 7bit 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 I'm certainly in favor of something like this. In my case, I still want the build to fail, but I want to send an e-mail to a text pager. Right now, I do this by doing an 'echo' to a file before a task starts, and a 'delete' of that file when the task finishes. After the build, I run Ant again with a different XML file that uses 'available' to find any of these temp files. If it finds any, it sends the e-mail. Crude, but it works... I'd much rather have the build do it's own thing... Conor MacNeill wrote: > > Peter Donald wrote: > > > > > I probably would have if it had been implemented as an antcall rather than as > > a container ;) > > I quite like the idea. I agree that error handling is pretty poor. We > can see that from the proliferation of failonerror attributes which have > been growing. People do want to continue running their builds when > things blow up. This would make most failonerror attributes obsolete, > though I don't think I'd suggest deprecating them :-) > > Of course, the same argument could be used for the "if" and "unless" > attributes and we may be on a slippery slope there (slippery slopes can > be fun though). > > You mentioned antcall, but the I'd say of of the most common patterns is > going to be: > > > > > > > > > doesn't really work for me. I thought of . The other > possibility might be a structure like this > > > > > > > > > > > > > > Whaddayareckon? > > Conor > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: