I invented that variable. I have no clue how to get a hold of that information.
- Original Message
From: Bob Archer <[EMAIL PROTECTED]>
To: Eric Fetzer <[EMAIL PROTECTED]>; Nant Users
Sent: Wednesday, May 28, 2008 12:13:55 PM
Subject: Re: [NAnt-users] Log file incomplet
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
her <[EMAIL PROTECTED]>; Eric Fetzer <[EMAIL PROTECTED]>; Nant Users
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 s
; 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: Wednesd
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)
E
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.csp
