-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Cole
Sent: donderdag 11 november 2004 0:01
To: 'Gert Driesen'; [EMAIL PROTECTED]
Subject: RE: [Nant-users] style parameter
Arg! :-)
I'm running NAnt 0.85 (Build 0.85.1762.0;
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Eric Deslauriers
Sent: woensdag 10 november 2004 23:53
To: Gert Driesen; [EMAIL PROTECTED]
Subject: RE: [Nant-users] NAnt copies more files than VS.NET
Thanks for the help. Unfortunately, I'm
Hi there,
I'm new to nant and am having trouble when referencing .dlls of my own
(as opposed to framework .dlls). I retrieve files from two VSS projects, one for
my supporting libraries and one for a web application that uses those libs. I
save the code files to two directories and create a
Title: Error trying to check out from VSS
I am new to NAnt and I am having problems checking source out from VSS.
SourceSafe is on my local drive at c:\vss
I can see and execute from a command line:
C:\ss dir -F- $/dev/build
$/dev/BUILD:
$_Build
$RAW Client Install
$/dev/BUILD/_Build:
Hello,
I need an advise...
Our company sells software components. Every our customer (depending on his
needs) may want to buy different combination of components.
I would like to create a script that would include these components into MSI
file depending on the value (true / false) of some
A program filename has '.' chars (for example: aspose.obfuscator),
ExecTask will consider it has directory part in filename, ExecTask
will add basedir as prefix.
Actually the aspose.obfuscator.exe is in path directory. Maybe below
codes will handle this correctly:
// ExecTask.cs
...
public
Ok.
And how do I solve this?
I've tried to replace the Ndoc libraries in the Nant/bin for the ones inside
my Ndoc/bin directory, but still doesn't work.
Suggestions?
Pedro Honório Silva.
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: terça-feira, 9 de Novembro
Title: 0.85 Dependency Resolution
With the following targets defined:
target name=A /
target name=B depends=A
call target=C/
/target
target name=C depends=A /
If I build target B, I get the following results:
NAnt 0.85 (Build 0.85.1775.0; nightly; 11/10/2004)
Copyright
Tom,
That is indeed the expected behaviour. If you want to avoid specific targets
from being executed more than once, you could use the
target::has-executed(name) function.
target name=A unless=${target::has-executed('A')} /
target name=B depends=A
call
Title: NUnit 2.2.1
I have been upgrading all of my build tools and noticed that NUnit has made another minor release. Are there plans to take this minor release into NAnt 0.85?
- Tom
Hello Jim,
Thank you for your help. I'm trying to make changes in my script according
to your hint. I found one problem. The next script:
property name=IsComponent1Selected value=0/
if propertytrue=ShouldIncludeComponent1
property name=IsComponent1Selected value=2 /
/if
features
feature
Title: Error trying to check out from VSS
This is an odd error. To me it seems like
it should work. That is assuming that vssget is loaded and it appears
to be loaded Have you gotten any help on this?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Frinder,
Let me point out that if you were to assume standard numbering
policies, then none of the NAnt releases would meet the requirement
that it be on a stable release. That's because version numbers less
than one (and the current nightly version is 0.85, not 8.5 or 85) are
normally considered to be
Thanks to Gert for answering my previous question about the Onfailure
property. I can confirm that the following project and subproject will
trigger the Onfailure task correctly:
Main Project:
project name=MainProject default=DoSubProject
property name=nant.onfailure value=OnFailure/
14 matches
Mail list logo
