RE: [nant-dev] SUBMISSION: Path Task

2003-12-15 Thread Damir Simunic
You'd probably want to call it loadextensions / then. Damir -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian MacLean Sent: Monday, December 15, 2003 4:06 AM To: Jaroslaw Kowalski Cc: Nant-Developers (E-Mail); William E Caputo Subject: Re: [nant-dev]

[nant-dev] Versions of nightly builds

2003-11-29 Thread Damir Simunic
I've noticed that nightly builds come with version number out of sync: just downloaded 0.8.4.31128, but properties of NAnt.exeshow 0.8.4.31114. Running nant -help shows 0.8.4.0. As a small convenience, do you think it would be possible to package the build in a version-numbered folder,

[nant-dev] fail task behavior and nant.onfailure

2003-11-29 Thread Damir Simunic
I've found some issues in handling forced failures in NAnt v0.8.4.31128. What happens is that I have a nant.onfailure task set. Somewhere in the build script, I'm failing the build with fail message=Failure reason / task. The onfailure handler calls a cleanup target that happens to have an

[nant-dev] Inconsistent behavior of include task?

2003-11-29 Thread Damir Simunic
I have 4 files: one in the root folder, three in a subfolder. In the root folder there is the main build file which includes one of the files in the subfolder. This other file includes another two. Thus: Main file has include buildfile="inc/included.build" / inc/included.build has:

RE: [nant-dev] MSBuild

2003-10-30 Thread Damir Simunic
MSBuild is obviously a child of Embrace Extend philosophy; being built-in in the next version of the framework will do wonders in terms of promoting the process of automated builds, which are critical to quality in our line of work. That is a good thing. Nant is already doing it. And that is even