Return-Path: 
 <ant-dev-return-20588-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 40286 invoked from network); 30 Nov 2001 17:02:03 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 30 Nov 2001 17:02:03 -0000
Received: (qmail 29889 invoked by uid 97); 30 Nov 2001 17:01:15 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 29682 invoked by uid 97); 30 Nov 2001 17:01:06 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 29648 invoked from network); 30 Nov 2001 17:01:03 -0000
Message-Id: <200111301701.fAUH11u15223@mail012.syd.optusnet.com.au>
Content-Type: text/plain;
  charset="utf-8"
From: Peter Donald <peter@apache.org>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Subject: Re: To fail or not to fail
Date: Sat, 1 Dec 2001 01:13:20 +1100
X-Mailer: KMail [version 1.3.1]
References: <m3vgfsv2th.fsf@bodewig.bost.de>
In-Reply-To: <m3vgfsv2th.fsf@bodewig.bost.de>
X-Wisdom-Cookie: .
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
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 Fri, 30 Nov 2001 23:52, Stefan Bodewig wrote:
> Hi,
>
> today I have committed two tasks that can cause build failures if
> certain conditions are met:
>
> * <input> makes the build fail, if the user ask for it
>
> * <waitfor> makes the build fail, if a given condition still doesn't
> pass after a given timeout.
>
> Some people may have been on this list when we discussed, whether
> <available> should be allowed to cause build failures.  That time, we
> said no, and I was one of the major proponents of "leave <fail> to
> <fail>".
>
> I still think that all build failures should be handled/caused by fail
> and would prefer if we removed the ability from the two above tasks.

+1

> If adding if/unless attributes to <fail> 

+1

> (or a nested <condition>
> element for the same task) 

-1

> is the price for this, I am willing to pay it.
>
> Others?
>
> Stefan

-- 
Cheers,

Pete

*-----------------------------------------------------------------------*
PROGRAM: n.  a magic spell cast over a computer allowing it to turn
one's input into error messages.  v.t.  to engage in a pastime similar
to banging one's head against a wall, but with fewer opportunities for 
reward.
*-----------------------------------------------------------------------*


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>