We perform a set of nested builds - outer nant invokes inner nant, each inner nant 
builds a different product with a different set of responsible developers.  When the 
inner nant build fails, we emit a summary failure notification to the responsible 
developers.  It would be helpful to include the specific failure reason / stack trace 
/ etc in this notification.

-----Original Message-----
From: Gert Driesen [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 28, 2004 4:29 PM
To: Breen, Patrick; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Access to failure reason text in onfailure target?


Patrick,

This information is not accessible from the build file, no.  What would you
use it for ?

Gert

----- Original Message ----- 
From: "Breen, Patrick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 28, 2004 7:05 PM
Subject: [Nant-users] Access to failure reason text in onfailure target?


Is there any property that contains the text of the failure reason (ie,
the summary info that Nant reports when a build fails) at the time an
onfailure target is invoked?  If not, is there a way to get at this
information via script?

Thanks -

Patrick


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id66&op=ick
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id149&alloc_id66&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to