: 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..
09 2:26 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] properties in functions
I'm coming to NAnt from an ant background, but I'm trying to adapt.
The documentation for
says that it's deprecated & recommends using functions instead.
I prefer to parameterize as much as p
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
-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] properties in functions
>
> I'm coming to NAnt from an ant background, but I'm trying to adapt.
>
-users] properties in functions
I'm coming to NAnt from an ant background, but I'm trying to adapt.
The documentation for
says that it's deprecated & recommends using functions instead.
I prefer to parameterize as much as possible, so I wrote
NAnt doe
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: [NA
I'm coming to NAnt from an ant background, but I'm trying to adapt.
The documentation for
says that it's deprecated & recommends using functions instead.
I prefer to parameterize as much as possible, so I wrote
NAnt doesn't like this much:
Unexpected token 'Dollar'.
Some time ago NAnt it was possible to pass properties by reference between
different NAnt scripts. I can see that this has now changed to be pass by value
which has broken a lot of my scripts. The only way I can get around this
functionality is to use environment variables which is very very a
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
>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 26, 2004 5:36 PM
Subject: [Nant-users] Properties Descriptions
Hello,
I am looking at converting my build files from .84 to .85 when the new
version releases. I was experimenting with a recent version of the
nightly code and noticed that pr
Hello,
I am looking at converting my build files from .84 to .85
when the new version releases. I was experimenting with a recent version of the
nightly code and noticed that properties can no longer have descriptions.
This worked on .84 and I was wondering if this can be added
bac
I'm running NAnt 0.84.
The documentation for the target is strange. It lists no input file to be
compiled property either optional or required. But, it does list a required output
property.
There is a fileset nested element, which implies that one target can
be used to compile a while set
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
be available in the next nightly
build.
Gert
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 05, 2004 9:57 AM
Subject: [Nant-users] Properties problem on task
Hi,
I have a bit of a problem with the task and can't see what&#x
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 problem with the task and can't see what's wrong.
Below is a copy of my build script and the associated output. According to
the documentation, I should be able to use a property value in my current
project to pass through top a new NAnt instance, but it seems to be failing
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
: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 19, 2004 4:16 PM
Subject: [Nant-users] Properties files
> Hello folks,
>
> I am new to Nant, but have done a bit in Ant compiling Java solutions. My
> question is, is there any equivalent to the task that
&
Hello folks,
I am new to Nant, but have done a bit in Ant compiling Java solutions. My
question is, is there any equivalent to the task that
existed in Ant?
The task in Nant only appears to let me set one property at a
time. I would like to set my build properties in a separate file and impor
Lowery" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 20, 2003 5:34 AM
Subject: [Nant-users] Properties problem with the schema task
> Hi there,
>
> I'm working with a recent nightly build of nant and I noticed that the
> schema task is now
-
From: "Ben Lowery" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 20, 2003 2:34 PM
Subject: [Nant-users] Properties problem with the schema task
> Hi there,
>
> I'm working with a recent nightly build of nant and I noticed that the
> sc
Hi there,
I'm working with a recent nightly build of nant and I noticed that the
schema task is now generating the name of the task as
"properties"
instead of "property". Any ideas on why the name is wrong? I stepped
through the code for the schema task, but didn't have any luck figuring out
wh
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
.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Sent: Thursday, February 13, 2003 5:04
PMTo: [EMAIL PROTECTED]Subject:
[Nant-users] Properties
Can I reuse a property? I want to
set a property then change it later in the
script.
I want to have one build file
Can I reuse a property? I want to set a property then
change it later in the script.
I want to have one build file that can switch
depending on a variable. Is this not what properties are for?
When I set the property it is always what ever I set
it to last. Can anyone tell me how I
36 matches
Mail list logo
