Return-Path: 
 <user-return-57583-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 25737 invoked from network); 11 Aug 2006 07:19:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 11 Aug 2006 07:19:27 -0000
Received: (qmail 90636 invoked by uid 500); 11 Aug 2006 07:19:24 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 90375 invoked by uid 500); 11 Aug 2006 07:19:23 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 90364 invoked by uid 99); 11 Aug 2006 07:19:22 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2006 00:19:22 -0700
X-ASF-Spam-Status: No, hits=0.3 required=10.0
	tests=MAILTO_TO_SPAM_ADDR,UNPARSEABLE_RELAY
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [193.201.183.194] (HELO sscd0001.dmz.huk.de) (193.201.183.194)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Aug 2006 00:19:13 -0700
Received: from sxf00001.lan.huk-coburg.de (unverified) by sscd0001.dmz.huk.de
 (HUK-COBURG Mailrelay2) with ESMTP id
 <T7a08ef862c0a9498831578@sscd0001.dmz.huk.de> for <user@ant.apache.org>;
 Fri, 11 Aug 2006 09:18:45 +0200
Received: from VEX00120.lan.huk-coburg.de ([10.131.152.134]) by
 sxf00001.lan.huk-coburg.de with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 11 Aug 2006 09:18:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Detecting <target> failure!
Date: Fri, 11 Aug 2006 09:18:35 +0200
Message-ID: 
 <1397E81F23832842BDD7B2D758D4B0B503256AAE@VEX00120.lan.huk-coburg.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Detecting <target> failure!
Thread-Index: Aca9D0Ox2ZrS0OEWQVO3esEftSvYxAABIOYA
From: "Rebhan, Gilbert" <Gilbert.Rebhan@huk-coburg.de>
To: "Ant Users List" <user@ant.apache.org>
X-OriginalArrivalTime: 11 Aug 2006 07:18:45.0250 (UTC)
 FILETIME=[61B01E20:01C6BD16]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


Hi,

1. ant-contrib has a <try> ... <catch> task

see http://ant-contrib.sourceforge.net/tasks/tasks/index.html
and Logic Tasks / Trycatch

2. some tasks f.e. <exec> have a resultproperty /outproperty
you can check that property with a condition

<condition property=3D"prop">                                        =20
     <equals arg1=3D"${resultproperty}" arg2=3D"0" />
    	</condition>
       <fail unless=3D"prop" message=3D"error -- rc !=3D 0 " />=20


or with ant-contrib if / else / then, example =3D

<!-- start ksh script -->    =20
<echo>${kshscript.prefix} activate ${projekt} ${lum} ${earfile}</echo>
        =20
<exec executable=3D"${plinkexec}" resultproperty=3D"rc.activate"
failonerror=3D"false">
...

you have to use failonerror=3D"false" here if you don't want an instant=20
Build failed and handle that error yourself !!

</exec>
      =20
<!-- ...check RC -->
<target name=3D"main" depends=3D"depends" >
      =20
<echo>+++ Returncode was_deploy_scm.ksh activate =3D=3D> ${rc.activate}
+++</echo>
<if>
   <not>
       <equals arg1=3D"${rc.activate}" arg2=3D"0" />
    </not>
    <then>
       <echo>+++ RC Shellscript !=3D 0 +++${line.separator}Abbruch :-(
!!</echo>
       <fail />
     </then>
</if>


or the depending target checks the property with

<target name=3D"foo" if=3D"${resultproperty}>
or
<target name=3D"foo" unless=3D"${resultproperty}>


Regards, Gilbert=20

-----Original Message-----
From: timujain [mailto:temujain2000@yahoo.com]=20
Sent: Friday, August 11, 2006 8:27 AM
To: user@ant.apache.org
Subject: Detecting <target> failure!


Hi there,
How can I detect <target> or <task> failure to call another <target> as
plan
B rather than failing the entire build?
--=20
View this message in context:
http://www.nabble.com/Detecting-%3Ctarget%3E-failure%21-tf2088943.html#a
5757429
Sent from the Ant - Users forum at Nabble.com.


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


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