Gert Driesen wrote:
Also, should we continue to throw a buildexception when a read-only property
is overwritten using another mechanism (eg. another task) ? I'd say yes,
but let me know what you think.
Sure -- its only the default mechanism thats causing the confusion.
Ian
Todd,
Can you send me a zip file containing the assemblies compiled with NAnt and
those compiled with VS.NET ?
Thanks !
Gert
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: woensdag 20 oktober 2004 20:53
> To: [EMAIL
My Nant build is successful and when I run my built Nant web
application locally it works correctly. If I move it to our development
webserver it half way works. The pages display but I can not get past our
login page that hooks up to an Oracle database. But if I build my
application with Visu
The file used with the task is a plain text
file with only the version number in it.
For example, create a new text file and rename it to:
'build.number'
Open the file with a text editor and add your version
number:
1.0.0.0
The task will read the version number, apply
its incrementing algorit
On Tue, 19 Oct 2004, Felice Vittoria wrote:
When I run this file I will get the following:
Property evaluation failed.
Expression: ${property::exists(rootdir)}
^^^
Property 'rootdir' has not been set.
Try:
Title: Message
Hi
all,
A quick question on
getting a file from vss to a local directory.
localpath="Output"
replace="true"
usemodtime="true"
writable="false"
I'm in favor of that! When's the 0.85 release?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gert Driesen
Sent: Wednesday, October 20, 2004 12:38 PM
To: 'Ian MacLean'; 'Thibaut Barrère'
Cc: 'Nant-Users (E-mail)'
Subject: RE: [Nant-users] Readonly properti
>From: "Gert Driesen" <[EMAIL PROTECTED]>
>Sent: Wednesday, October 20, 2004 1:38 PM
>Should we also deprecate the "overwrite" attribute on the task
>(and remove it after the 0.85 release), as a "property::exists(...)" unless
>condition could be used instead ?
Yes, particularly because of all th
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Gert Driesen
> Sent: woensdag 20 oktober 2004 19:38
> To: 'Ian MacLean'; 'Thibaut Barrère'
> Cc: 'Nant-Users (E-mail)'
> Subject: RE: [Nant-users] Readonly properties, overwrite attribute
>
>
>
Title: Newbie: Compiling 'Hello World' in managed c++ using cl and link?
Hi,
I'm trying to wrap my head around compiling managed c++ using the and tasks. There's a managed c++ project that needs to be part of my build, but I didn't write it - I don't know c++, I'm a c# developer. That mea
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Ian MacLean
> Sent: woensdag 20 oktober 2004 18:32
> To: Thibaut Barrère
> Cc: Nant-Users (E-mail)
> Subject: Re: [Nant-users] Readonly properties, overwrite attribute
>
> Didn't we agree to not
Didn't we agree to not throw this error anymore - and just warn as was
the previous behaviour ? I guess the change hasn't gone in yet. If I get
some time tomorrow I'll do it.
Ian
Thibaut Barrère wrote:
Hi,
I've been struggling around a while after updating a 5 month old nant
to the latest versio
Hi Clayton,
- Original Message -
> > However, it seems that task ignores the
> > "cvsroot" attribute!!! Is this a Nant bug?
> This may be a bug...this task should actually be changed to grab the
> Root from the cvs folder and should not require a cvsroot at all. I
> will try to get th
Sorry, I thought the below section of code out of the sysinfo task would
spit out the properties that are set. I am actually not interested in the
path variable. I was just using it as a test. Thanks again for the help.
// display the properties
if (Verbose) {
foreac
Charles,
>>> in the verbose setting for the sysinfo task. It doesn't display the environment
>>> variable properties that were set.
Actually, the verbose attribute has nothing to be with the information _collected_ by
sysinfo or the environment variables. All NAnt tasks have a verbose attribu
Merrill,
Thanks. This works. So, a potential bug would be in the verbose setting
for the sysinfo task. It doesn't display the environment variable
properties that were set. After a quick glance at the source, it looks like
it should display these values. If I get a chance I will look at why t
Gert,
Thanks for you input. I have tried 'path' and 'PATH'. Neither work. As
you can see in the log file the environment variables are not even loading.
My work around is to use the environment::get-variable() function so I will
stick with that.
Thanks,
Charlie
-Original Message-
From
Charles,
Despite the fact that sys.env.PATH is the example given in the NAnt
documentation, and despite the fact that I thought that's what I used before; when I
checked, on my machine the environment variable is "Path" (i.e., initial caps only).
So, when I tried ${sys.env.Path}, it worked.
Hi,
> However, it seems that task ignores the
> "cvsroot" attribute!!! Is this a Nant bug?
This may be a bug...this task should actually be changed to grab the
Root from the cvs folder and should not require a cvsroot at all. I
will try to get this change in sometime this week/ weekend when I
Charles,
NAnt properties are case-sensitive. Try using "sys.env.PATH".
However, an even better solution would be to use the
environment::get-variable() function
eg. environment::get-variable("PATH")
Hope this helps,
Gert
- Original Message -
From: "Bassham, Charles" <[EMAIL PROTECTED
Tried it with build 1677 (0.85). I also got the latest binaries and it
still didn't work. I have attached a simple repro of what I am doing plus
the output. I have a work-around but it would be nice if I could figure out
what I was doing wrong.
Thanks for any help,
-Charlie
-Original Messa
Gary,
What version of NAnt are you using (as we should provide a more meaningful
and less verbose error message) ?
Gert
- Original Message -
From: "McCullough, Gary" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 20, 2004 3:23 PM
Subject: RE: [Nant-users] URI forma
I figured out what it was. I was looking
at the wrong solution task. The one I was executing was using EnableWebDav rather
than WebMap. I still don’t know what the error means, but the solution
task worked once I repaired it with WebMap.
Gary McCullough
From:
[EMAIL
Things to write today.
I'm using a foreach over a fileset of projects to generate ndoc for
each of these projects.
I override a property inside the loop (as a temporary variable). I'm
displaying it just after to check if it was properly set and it's
working fine
But when I pass this property to
More info; part of the script I use below :
-
-
The beginning of the must-publish-project function :
--
Hi again,
did anyone had issues with current path (ie the place where you are
when a task is finished) in their script after a recent upgrade of
nant ?
I did not investigate much already as I don't have time for this now
(I used a simple workaround), but after upgrading nant (previous
release was
Hi,
I've been struggling around a while after updating a 5 month old nant
to the latest version.
I've been confused about what I get when overriding a property from
the command-line (which we use a lot for instance with cruisecontrol) :
"Read-only property "xxx" cannot be overwritten."
Don't re
27 matches
Mail list logo
