Re: [Nant-users] Changing failonerror on the fly

2004-12-16 Thread Troy Laurin
Eric Deslauriers wrote: What I need to do with the above snippet is change test’s failonerror to TRUE when not doing code coverage, but to FALSE when doing codecoverage, then pass the fail back to codecov to propogate out. Basically like catching and rethrowing an exception. Thanks!, Eric Eric

Re: [Nant-users] Changing failonerror on the fly

2004-12-16 Thread Troy Laurin
John Hardin wrote: On Tue, 2004-12-14 at 04:40, Troy Laurin wrote: The cleanest solution (IMHO) was to create a custom try/catch/finally task... your codecov target becomes: GACK! Where is this documented? Is this part of the standard syntax for all targets? -

Re: [Nant-users] Changing failonerror on the fly

2004-12-16 Thread Gert Driesen
> - Original Message - > From: "Troy Laurin" <[EMAIL PROTECTED]> > To: "John Hardin" <[EMAIL PROTECTED]> > Cc: "NAnt Users mailing list" <[EMAIL PROTECTED]> > Sent: Wednesday, December 15, 2004 3:20 PM > Subject: Re: [

RE: [Nant-users] Changing failonerror on the fly

2004-12-14 Thread Eric Deslauriers
Troy, Thanks for the head's up. As soon as we move to 0.85, I'll plunk that in. It is a great solution. Eric D > The cleanest solution (IMHO) was to create a custom try/catch/finally > task... your codecov target becomes: > > > > > > > > > > > > The tr

Re: [Nant-users] Changing failonerror on the fly

2004-12-13 Thread Merrill Cornish
Eric, Properties are immutable ONLY if their readonly attribute has been set to true. Properties which are created by virtue of being -D: command line arguments are automatically readonly. However, properties that YOU create are readonly ONLY if you override the default of read/write and set