Return-Path: 
 <ant-user-return-24235-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 90326 invoked from network); 23 Aug 2002 14:00:09 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 23 Aug 2002 14:00:09 -0000
Received: (qmail 11821 invoked by uid 97); 23 Aug 2002 14:00:27 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 11798 invoked by uid 97); 23 Aug 2002 14:00:26 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 11737 invoked by uid 98); 23 Aug 2002 14:00:22 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: <2DAFF28F562AD4119B0E00508B5F049F0222A3FC@AMSEXCH01>
From: Tibor  Strausz <Tibor.Strausz@tridion.com>
To: 'Ant Users List' <ant-user@jakarta.apache.org>
Subject: RE: task results as conditionals
Date: Fri, 23 Aug 2002 16:01:01 +0200
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

look interesting

> -----Original Message-----
> From: Ken Arnold [mailto:arnold@moonhill.org]
> Sent: Thursday, August 22, 2002 7:23 PM
> To: ant-user@jakarta.apache.org
> Subject: task results as conditionals
> 
> 
> I as running down the (apparently old) question of how to run 
> arbitrary 
> tasks whose failure doesn't stop the build.  I find that the idea of 
> putting "failonerror" on all tasks is considered the solution.  While 
> this will work for me, I tried something else first and it 
> seems to me 
> to be more powerful, and which I can't find in the mail archive.
> 
> If you consider an ant task's result to map to true on 
> success and false 
> on failure, then I could use <conditional> to do arbitrary 
> combinations, 
> as in:
> 
> <conditional>
>      <or>
>          <javac ..../>
>          <exec ..../>
>      </or>
> </conditional>
> 
> This would run javac, and if it failed, exec some program 
> (possibly to 
> analyze the error output)
> 
> The view would be that an arbitrary task in a conditional 
> would be run 
> for its result, and therefore it would be up to the 
> conditional (or its 
> user) to decide what to do with that failure.
> 
> I can imagine this being used in other contexts, and because of the 
> conditional logic, can be more powerful than a simple 
> fail/nofail on a 
> single target.
> 
> Possibly this comes from some conceptual error on my part, 
> but if so, I 
> figure I might as well go for public humiliation over private error.-)
> 
> 		Ken Arnold
> 
> 
> --
> To unsubscribe, e-mail:   
> <mailto:ant-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:ant-user-help@jakarta.apache.org>
> 

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