I've incorporated everyone's comments and am rolling the tarball now.
Thanks for the feedback.
John C Barstow
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free boo
Yeah - the behavior is now the same when you specify basedir="." and
when you leave it off. Before, leaving out the basedir= attribute would
treat the current directory as relative to the script, but using
basedir="." would put you in the current working directory. Now, both
will leave you in
: [nant-dev] For review - 0.8.3 rc1 release notes
0.8.3rc1 release notes (plain text format)
---
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.para
really ? I thought it was always based on the location of the script.
That seems more valid to me. I wouldn't want my build having different
behaviour because I ran nant from a different directory.
Ian
I have noticed that NAnt has started taking the basedir relative to
the location of the NAnt
I have noticed that NAnt has started taking the basedir relative to the
location of the NAnt script, rather than the working directory of where
NAnt was run from. This seems to have taken place somewhere in 0.8.3
development.
John Barstow wrote:
0.8.3rc1 release notes (plain text format)
Ple
just started looking thu but I see immediatly that mcs is mentioned as
a new task.
there was a mcs task that has since been removed once we implemented
framework support. On mono the csc task runs mcs.exe behind the scenes.
Hmm I see you mention this later on in the Changed Tasks section.
Other
0.8.3rc1 release notes (plain text format)
Please review and post your comments to the mailing list. I'm starting the
release process tonight with the 0.8.3 branch. It's a bit more detailed than
previous logs, but I think I got all the significant changes that might
impact an unwary user.
John C
