Return-Path: 
 <ant-dev-return-31831-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 75114 invoked from network); 6 May 2002 18:29:38 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 6 May 2002 18:29:38 -0000
Received: (qmail 15845 invoked by uid 97); 6 May 2002 18:29:39 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 15752 invoked by uid 97); 6 May 2002 18:29:37 -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 15681 invoked by uid 98); 6 May 2002 18:29:36 -0000
X-Antivirus: nagoya (v4198 created Apr 24 2002)
Subject: assert task?
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 6 May 2002 14:29:31 -0400
content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: 
 <B53B8D5F63FE6C48B6DDC2D25203FA880449F9@exchang2k.internetivity.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Ant 1.6 alpha build problems
Thread-Index: AcH1KqOHYeyhwF+VROaz863UYZ0KEwAAAfow
From: "Robi Khan" <rkhan@databeacon.com>
To: "Ant Developers List" <ant-dev@jakarta.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi,
I've been following the back and forth on whether the fail task should =
take an if/unless attribute. The counterargument seems to be that this =
is a slippery slope that would lead to all tasks having if/unless.

Perhaps. What I've done in our builds is define an assert task that =
works with the existing property and conditional stuff.

e.g.
	<available file=3D"fubar.xml" property=3D"isXmlThere"/>
	<assert condition=3D"isXmlThere" message=3D"Could not find fubar.xml =
file"/>

The implementation is too trivial to worth mention. And it has all the =
benefits that assert has in programming languages. For example, I use it =
often to validate input parameters to targets. In general I think it's a =
good fit for larger Ant projects.

Comments?

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