Return-Path: 
 <user-return-40760-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 93960 invoked from network); 3 Feb 2004 19:12:49 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 3 Feb 2004 19:12:49 -0000
Received: (qmail 93593 invoked by uid 500); 3 Feb 2004 19:11:42 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 93543 invoked by uid 500); 3 Feb 2004 19:11:42 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:user-subscribe@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 93483 invoked from network); 3 Feb 2004 19:11:41 -0000
Received: from unknown (HELO ext-nj2gw-1.online-age.net) (216.35.73.163)
  by daedalus.apache.org with SMTP; 3 Feb 2004 19:11:41 -0000
Received: from int-nj2gw-6.online-age.net (int-nj2gw-6 [3.159.236.70])
	by ext-nj2gw-1.online-age.net (8.12.9/8.12.9/990426-RLH) with ESMTP id
 i13JBiIM005562
	for <user@ant.apache.org>; Tue, 3 Feb 2004 14:11:45 -0500 (EST)
Received: from ncwlmx01nege.wilm.ge.com (localhost [127.0.0.1])
	by int-nj2gw-6.online-age.net (8.12.9/8.12.8/990426-RLH) with ESMTP id
 i13JBcMd009403
	for <user@ant.apache.org>; Tue, 3 Feb 2004 14:11:42 -0500 (EST)
Received: by ncwlmx01nege.wilm.ge.com with Internet Mail Service (5.5.2653.19)
	id <ZBW8TLVF>; Tue, 3 Feb 2004 14:11:29 -0500
Message-ID: 
 <42C9EFEA1737D511BA420008C78641510CD8D5C2@ncwlmx01nege.wilm.ge.com>
From: "Conelly, Luis (PS, GNF, Contractor)" <Luis.Conelly@gnf.com>
To: Ant Users List <user@ant.apache.org>
Subject: RE: Question about failonerror
Date: Tue, 3 Feb 2004 14:11:28 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C3EA89.86942702"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

------_=_NextPart_001_01C3EA89.86942702
Content-Type: text/plain;
	charset="iso-8859-1"

If you want to know what's failing and have an alternative before the process finishes, you can use ant-contrib's[1] <trycatch>. It will not prevent your tasks fail, but you'll have some control after failing and an alternative way to execute some other stuff.

Regards
Luis

BTW, I agree with Dominique ;)

[1] http://ant-contrib.sourceforge.net/

-----Original Message-----
From: Dominique Devienne [mailto:DDevienne@lgc.com]
Sent: Tuesday, February 03, 2004 1:05 PM
To: 'Ant Users List'
Subject: RE: Question about failonerror


> From: Tony Brusseau [mailto:brusseau@cyc.com]
> 
> I just wrote a target that calls junit and
> has different behaviors depending on whether of
> not junit succeeded. To do this I used the
> following attributes:
> 	haltonfailure="off"
>         failureproperty="test-failed"
>
> I'd like to have the same behevior for
> compling, cleaning, "cvsing", installing, etc.

Why? Doesn't an unsuccessful compile warrant a failure?

The only time I ever use failonerror="false" is to allow
generating the testing report with <junitreport>, so that
the developer can look at the failures in the report, and
I then actually fail the build.

That's it. Everything else that fails should fail the build,
and you should reconsider doing anything different, IMHO. --DD

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

------_=_NextPart_001_01C3EA89.86942702--