----- Original Message ----- From: "Mike Castle" <[EMAIL PROTECTED]> To: "Ant Users List" <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
