Hi Damir,
According to an email I found
(http://www.geocrawler.com/archives/3/14603/2002/9/0/9638108/) the
correct behavior for is to set the included file's basedir
to the basedir of the file including it.
This is not the case. Files should always be included relative to the
file doing the
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
inc/included.build
has:
According to an
email I found (http
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Damir
Simunic
Sent: 29. studeni 2003 20:59
To: [EMAIL PROTECTED]
Subject: [nant-dev] task behavior and nant.onfailure
...
In addition, in all three scenarios any message after the task
is never printed ou
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
task. The onfailure handler calls a cleanup target that happens to have an
error.
If the call to the cleanup
I've noticed that
nightly builds come with version number out of sync: just downloaded
0.8.4.31128, but properties of NAnt.exe show 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 folde
