Have you tried creating an on.failure task and just echoing out that variable 
to put it into the log?

 

________________________________

From: Eric Fetzer [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 28, 2008 2:11 PM
To: Bob Archer; Nant Users
Subject: Re: [NAnt-users] Log file incomplete

 

It already is.  It seems like this information should be locked inside a 
variable like ${build.failure.reason} or something like that.  Solution kicks 
it out to Build.Failure, but it doesn't log a reason.



 

----- Original Message ----
From: Bob Archer <[EMAIL PROTECTED]>
To: Bob Archer <[EMAIL PROTECTED]>; Eric Fetzer <[EMAIL PROTECTED]>; Nant Users 
<nant-users@lists.sourceforge.net>
Sent: Wednesday, May 28, 2008 11:59:14 AM
Subject: RE: [NAnt-users] Log file incomplete

Actually, sorry my bad. I read that too fast. Are you using the solution task? 
If so, perhaps you can set it to verbose.

 

BOb

 

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Archer
Sent: Wednesday, May 28, 2008 1:55 PM
To: Eric Fetzer; Nant Users
Subject: Re: [NAnt-users] Log file incomplete

 

There is no log in the case that a valid project/build file isn’t loaded, or 
the XML doesn’t parse. 

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Fetzer
Sent: Wednesday, May 28, 2008 1:52 PM
To: Eric Fetzer; Nant Users
Subject: Re: [NAnt-users] Log file incomplete

 

As an example, here's something that showed up at the end of a manual build 
that won't for an automated one (even though I keep the record opened until the 
very end):

 

            BUILD FAILED - 0 non-fatal error(s), 3 warning(s)

            Error loading project 'D:\Builds\MyProject\MyProject.csproj'.
                Data at the root level is invalid. Line 1, position 1.

 



 

----- Original Message ----
From: Eric Fetzer <[EMAIL PROTECTED]>
To: Nant Users <nant-users@lists.sourceforge.net>
Sent: Wednesday, May 28, 2008 11:38:33 AM
Subject: [NAnt-users] Log file incomplete

Sometimes when I run my builds automatedly and go to get information about what 
caused it to fail, it doesn't show up in the build log.  So, I have to run it 
manually to see what the last thing NAnt said after the build file already 
closed.  Is there a way to get that infomation into the build log?

 

 

 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to