Return-Path: 
 <ant-user-return-28242-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 80879 invoked from network); 14 Jan 2003 01:30:43 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 14 Jan 2003 01:30:43 -0000
Received: (qmail 23276 invoked by uid 97); 14 Jan 2003 01:31:59 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 23250 invoked by uid 97); 14 Jan 2003 01:31:58 -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 23206 invoked by uid 98); 14 Jan 2003 01:31:57 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: <000801c2bb6c$c7a7a4f0$1219570f@ranier>
From: "Steve Loughran" <steve_l@iseran.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>,
   "Mike Castle" <dalgoda@ix.netcom.com>
References: <fc9bfxhst.ln2@thune.mrc-home.org>
 <007801c2bb41$0791cfe0$1219570f@ranier>
 <20030113231332.GA971@thune.mrc-home.com>
Subject: Re: detecting build failures with OUT exiting
Date: Mon, 13 Jan 2003 17:32:16 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-MailScanner: Found to be clean
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


----- Original Message -----
From: "Mike Castle" <dalgoda@ix.netcom.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
Sent: Monday, January 13, 2003 15:13
Subject: Re: detecting build failures with OUT exiting

> > There are <try> and <catch> tasks in ant-contrib.sf.net; these let you
wrap
> > the <ant> calls. Covered on p256 of the book, btw.
>
> Ack!  Information overload.  And on such a memorable page number too!
>
> But this definitely looks like what I was looking for.  Thanks!
>
> I take it that this is a different implementation of the same idea posted
> by Dale Anson elsewhere in this thread?


not if he used <try> and <catch>

>
> > > So, if a file fails to compile, the automated build exits, and I can't
> > send
> > > off an email from inside ant to the appropriate individuals telling
them
> > > they need to buy the next round.
> >
> > MailLogger is the way to do this. I like your 'your broke the build'
> > punishment policy.
>
> The current script uses the XmlLogger and saves that off.  If there is
> an error it sends an email saying "go here."  I'll probably keep that
> method and use the <mail> task.  They get annoyed if I even hint at
> changing stuff to drastically, so I don't want to change what they
receive.

ok, but the purpose of the mail logger is to send out success/failure
emails, which is really what you want to do.

> Considering the number of emails we've sent out today, someone may have to
> just bring in a pony keg later this week....

Wait till you add <checkstyle> to the build...


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