Julian Suggate wrote:
Ignoring the typo, I suspect that the basedir attribute of the project element doesn't evaluate expressions.... @echo off
SET BUILD_PATH=C:\Dev nant -v -buildfile:HF.build %1
Using different batch files on different machines, developers can have different build locations (out of convenience for the team).
The Problem ------------------- In the NAnt build script, I have the following project decl:
<project name="TestProject" default="All"
basedir="${environement::get-variable('BUILD_PATH')}"
>
In any event, I think you're going about this the wrong way. Instead of SET BUILD_PATH=C:\Dev just use cd C:\DEV or even cd %BUILD_PATH%
and then skip the basedir attribute on the project task.
Your life will be much, much easier if you always make sure that the top level NAnt build script executes in the directory in which it lives. If you don't do this, then sooner or later something called by NAnt won't have the right working directory.
Better yet, get rid of the .bat file entirely, except perhaps for scheduling automatic builds. It's easy enough to type nant. Is there any other context where you need the .bat file?
Gary
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
