: Wednesday, April 08, 2009 11:42 AM
To: Steve Kapinos; Nathan Franzen; nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] properties in functions
Actually, in the original posting, version-info-script was a property
that was initialised with the name of the file in question, rather than
bei
ginal Message-
From: Steve Kapinos [mailto:steve.kapi...@tandberg.com]
Sent: 08 April 2009 14:46
To: Nathan Franzen; nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] properties in functions
Don't use ${ } inside an existing expression. You use it once to say
this in an expression..
Don't use ${ } inside an existing expression. You use it once to say
this in an expression.. from there Nant knows how to find the keywords,
etc
So instead of
Use
Assuming 'version-info-script' is the name of the file you are looking
for. Strings put in ' ' , function names and prop
Your close, you don't need the ${} around the property name inside and
expression.change:
to:
On Tue, Apr 7, 2009 at 2:26 PM, Nathan Franzen wrote:
> I'm coming to NAnt from an ant background, but I'm trying to adapt.
> The documentation for
>
> says that it's deprecated & recomm
OK, got it! Thanks everyone.
-Nate
On Tue, Apr 7, 2009 at 3:01 PM, Gert Driesen wrote:
> Hi Nathan,
>
> In expressions, properties must be references without braces.
> For example:
>
>
> />
>
>
> Hope this helps,
>
> Gert
>
> -Original Message-
> From: Nathan Franzen [m
Hi Nathan,
In expressions, properties must be references without braces.
For example:
Hope this helps,
Gert
-Original Message-
From: Nathan Franzen [mailto:nfran...@gmail.com]
Sent: dinsdag 7 april 2009 20:26
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users
Once you are already in an expression you don't escape the properties
again. Use this:
BOb
> -Original Message-
> From: Nathan Franzen [mailto:nfran...@gmail.com]
> Sent: Tuesday, April 07, 2009 2:26 PM
> To: nant-users@lists.sourceforge.net
> Subject: [NAnt-users] properties in
Merrill Cornish wrote:
Jim,
How would this differ from using XML comments in the build
files?
Clumsiness, or lack thereof.
XML comments are verbose and stand on a level with the elements they
are supposed to be commenting on. Therefore, it's not always clear
who they apply to.
Personally, there's
Title: RE: [Nant-users] Properties Descriptions
Merrill,
/* ... */ and // ... style comments cannot be pinned to a language element any more than a style comment can. I think it is generally accepted that comments precede the thing that they describe.
Having said that, I suppose the
t;
Reply-To: Merrill Cornish <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: [Nant-users] Properties Descriptions
Date: Fri, 27 Aug 2004 09:43:38 -0500 (GMT-05:00)
Jim,
>>> How would this differ from using XML comme
other issues unless this is a seriously low-hanging fruit fix.
> -Original Message-
> From: Merrill Cornish [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 27, 2004 10:44 AM
> To: Holmes, Jim; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE
Jim,
>>> How would this differ from using XML comments in the build files?
Clumsiness, or lack thereof.
or
versus
XML comments are verbose and stand on a level with the elements they are supposed to
be commenting on. Therefore, it's not always clear who they
2004 10:05 AM
To: Gert Driesen; Shaber,David; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Properties Descriptions
Gert,
>>> [property descriptions] has never been supported by NAnt ... NAnt now reports
>>> unknown elements and attributes.
Perhaps NAnt could allow, but ig
Gert,
>>> [property descriptions] has never been supported by NAnt ... NAnt now reports
>>> unknown elements and attributes.
Perhaps NAnt could allow, but ignore, a "comment" attribute on all tasks.
Merrill
---
SF.Net email is sponsored by
David,
This has never been supported by NAnt. What has changed in recent nightly
builds, is that NAnt now reports unknown elements and attributes. Previous
versions of NAnt did not have this capability.
Gert
- Original Message -
From: "Shaber, David" <[EMAIL PROTECTED]>
To: <[EMAIL PROT
MAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, April 05, 2004 10:48 AM
Subject: RE: [Nant-users] Properties problem on task
Great, Thanks Gert.
At the risk of seeming overly cautious, could I ask how stable the nightly
builds are? Am I safe to use them as the basis of building our soft
[mailto:[EMAIL PROTECTED]
Sent: 05 April 2004 09:40
To: Bill Martin; [EMAIL PROTECTED]
Subject:Re: [Nant-users] Properties problem on task
Bill,
This was actually a bug in the nant task. The properties you specified as
nested elements, were evaluated in the context of the new
Bill,
This was actually a bug in the nant task. The properties you specified as
nested elements, were evaluated in the context of the new project. I
changed this to evaluate the properties in the current build file, when the
property is not dynamic.
This fix has been committed to cvs and will b
Do you need to set readonly="true" on the properties you are passing in?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 05 April 2004 07:58
> To: [EMAIL PROTECTED]
> Subject: [Nant-users] Properties problem on task
>
>
> Hi,
>
> I have a bit of a p
Title: RE: [Nant-users] Properties files
All,
Quick question...
I am getting this exception when checking out code to label in VSS. I have come to the conclusion that when checking out via the , it will not overwrite and will fail if the files already exist. Is this accurate?
So, if
Marvellous, that will do the job nicely thanks Jarek.
Cheers,
Bill
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]
Sent: 19 March 2004 15:38
To: Bill Martin; [EMAIL PROTECTED]
Subject:Re: [Nant-users] Properties files
It is possible through task
It is possible through task. You simply have all your properties
in a separate buildfile:
properties.build
And you use it like this:
main.build:
Hope it helps.
Jarek
- Original Message -
From: <[
Ben,
The current version of the NAntSchema task is not terribly useable. There
are some serious issues with how it deals with collections (which are
relatively new to NAnt and used a lot now) and arrays. I'm pretty sure this
is the existing problem. I am working on some new util classes that shoul
I assume this has something to do with the fact that we also use the
property task as an element in the task to allow a user to set
specific properties in the newly create NAnt project (while still reusing
the code in PropertyTask).
Scott, can you verify this ?
Gert
- Original Message -
PROTECTED]
Subject: Re: [Nant-users]
Properties
I think what
you want is this:
-->
cause build
files evaluate "global tasks" (any non-target task at th
Note: 1-4 are "global
tasks"
1.) prop debug
true
2.) prop debug
false
3.) prop debug
haha
4.) prop debug
hehee
5.) target
first
- Original Message -
From:
Dave Lloyd
To: 'Miller, Kevin' ; [EMAIL PROTECTED] ; [EMAIL PROTECTED]
ller, Kevin
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 6:36 PM
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Nant-users]
Properties
Once
you set a property I believe it is scoped to the entire project meaning it is
visible everywhere. You can update it later on
Once
you set a property I believe it is scoped to the entire project meaning it is
visible everywhere. You can update it later on in your script, no
problem.
Note,
If you set a property via the commandline inputs those properties are ReadOnly
and cannot be changed. You can try to update R
28 matches
Mail list logo
