From ant-dev-return-12107-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org Tue Mar 27 19:21:46 2001 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 59217 invoked by uid 500); 27 Mar 2001 19:21:45 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 59208 invoked from network); 27 Mar 2001 19:21:44 -0000 Message-ID: <047e01c0b6f3$2c7ad710$7691070f@cv.hp.com> From: "Steve Loughran" To: References: Subject: Re: [DISC] core extensions Date: Tue, 27 Mar 2001 11:21:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N ----- Original Message ----- From: "Stefan Bodewig" To: Sent: Tuesday, March 27, 2001 04:47 Subject: Re: [DISC] core extensions > > * specify an onfail task or target that runs in case of a build > > failure. > > And what if that one fails? -1 the onfail target specified in the failure task gets called, and so on: Where the concept gets confusing is in dependencies. Should failure tasks have all their dependencies executed? It should only be when things start going wrong that they are called, but then what happens when the dependent tasks start to fail. Should the 'onfail' task of the target highest up the tree be the default 'handler' for failures (like VB's ON ERROR GOTO hack)? It soon gets really complex, in the absence of the 'backtracking model of prolog' -steve