Hello,
We have a nant build script that has a to
give locations of non-standard project locations.
Here’s what we have:
mainline source is D:\foo\mainline
branch source is d:\foo\branch1
urls are currently pointing to “d:\foo\branch1”
(they would need to be pointing to d:\f
Okay, so the following will fail if the directory does not
exist
the following will pass if the directory does exist
what if I want it to be just like java’s ant where I
am doing a clean target and I want it to pass if
The direct
Evan Levy said:
> use the task "output" parameter to send the program's output to a
> file.
In my experience that does NOT suppress output to the NANT log - it goes
to both. Has that bug been fixed?
--
John Hardin
Development and Technology group (Seattle)
CRS Retail Systems, Inc.
3400 188th S
This may be a newbie problem, but I am unable to specify the
build target on the command line to nant.
Here is the build file:
‘nant’…. Runs the test target, as
Hi guys,
I'm currently spawning NAnt processes from a MSDOS .bat file
like:
NAnt
-buildfile:.\KMD.NI.SdpiEws.Clean.build
-logfile:.\log\Clean.log
"-D:ver.conf=0.2.0.1"
"-D:bld.conf=Release"
Clean
I want to move this to a Nant master.build file,
like:
The problem seems
Title: Re: [Nant-users] Developers using NAnt Directly
I didn't mean to imply that (our)
developers shouldn't or don't build locally. In our company in fact they
do and can catch code errors this way before checking code in. Whether or
not they build locally with Nant is the issue, and i
On 10/20/05, Evan Levy <[EMAIL PROTECTED]> wrote:
> This is what we do. Developers develop with Visual Studio, and the
> build automation happens with Nant on the server pulling code from
> source control. In fact, our developers don't really need to build
> locally at all (but they do anyway).
On 10/20/05, Anderson, Kelly <[EMAIL PROTECTED]> wrote:
> As a follow up question though... about the "clean" target, does the
> clean target typically delete the source files so that they have to be
> retrieved from revision control by scratch, or just the obj, lib, exe
> and other intermediate fi
This is what we do. Developers develop with Visual Studio, and the
build automation happens with Nant on the server pulling code from
source control. In fact, our developers don't really need to build
locally at all (but they do anyway). They can launch a server-side Nant
build from a custom web
Well, I think that comes down to a cost/benefit analysis. If the benefits of
building with NAnt outweigh the cost of learning, then
your developers will likely hop on the bandwagon.
I phased it in at my workplace, where we do mostly web apps. Our devs use
VS.NET for coding, testing, and debugg
The developers on my team are used to working in the Microsoft IDE with
sln and vcproj files. With NAnt, I have been able to use the
task to compile code using this familiar environment. I don't want
everyone on the team to be REQUIRED to learn NAnt to get their job done.
So my thought is that th
I think you have made a very persuasive argument here for doing a clean
every time. I'm not worried about how long the unit tests take to run,
since we don't have any yet ;-) sad but true.
As a follow up question though... about the "clean" target, does the
clean target typically delete the source
I have a simple question. I am getting this error using NAnt 0.85 (Build
0.85.1932.0; rc3; 4/16/2005) along with Nunit 2.2.0.0.
In the Nant documentation it says to add assembly binding to a test config
file. But I am building against the 2.2.0.0 nunit.framework.dll. Can anyone
please provide
Your XSLT sounds interesting. Would you consider sharing it? Which wiki does
it markup for?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ryan Davis
Sent: Wednesday, October 19, 2005 3:47 PM
To: 'Troy Laurin'; 'Anderson, Kelly'
Cc: nant-users@lists.sourc
Getting a little off topic, but you mentioned using the script as documentation:
>> Indeed, a reasonably well written NAnt script could even (with a small
>> stretch of imagination) be considered to be the documentation.
>> Even if you aren't familiar with the structure of NAnt, something like
>>
Seems like this project just plain won't play with
NAnt
I
had 2 more intermittent errors
one
was a dependent assembly not being found.
second one is
BUILD FAILED
Unexpected error while
compiling project 'GateCycleMain' Item has already been
added. Key in dictionary:
"E:\GC\RootBuil
By adding NAnt and Contrib in a tools subdirectory under the root directory
containing your solution you can remove both these tools from the bootstrap.
CCNet and revision control are still required in the bootstrap. The idea is
that CCnet monitors this solution root directory and GETs the NAnt
17 matches
Mail list logo
