ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: detecting build failures with OUT exiting
Date Tue, 14 Jan 2003 01:32:16 GMT

----- Original Message -----
From: "Mike Castle" <>
To: "Ant Users List" <>
Sent: Monday, January 13, 2003 15:13
Subject: Re: detecting build failures with OUT exiting

> > There are <try> and <catch> tasks in; these let you
> > 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
> > > 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

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:   <>
For additional commands, e-mail: <>

View raw message