Actually, this is not a bug. It's working
as designed. Here's the URL to the property help page:
http://nant.sourceforge.net/nightly/help/tasks/property.html
What
you need to do is set overwrite="false" and it should work.
Felice
-Original Message-From:
[EMAIL PROTECTED]
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 22, 2004 11:23 PM
Subject: [Nant-users] can't overwrite property
Hi there,
why can't properties be overwritten?
my code: or
run: nant -D:path=c:\temp
Nant says:
Hi there,
why can't properties be overwritten?
my code: or
run: nant -D:path=c:\temp
Nant says: readonly property
path can't be overwritten.
is it a bug in 0.85.1724
(09-20 build)?
thx
Gert Driesen wrote:
- Original Message - From: "Gary Feldman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 13, 2004 5:53 PM
Subject: Re: [Nant-users] Can't overwrite property when readonly not set
Although a node with nested element wou
- Original Message -
From: "Gary Feldman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 13, 2004 5:53 PM
Subject: Re: [Nant-users] Can't overwrite property when readonly not set
>From: "Ian MacLean" <[EMAIL PROTECTED]&
>From: "Ian MacLean" <[EMAIL PROTECTED]>
>Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> This issue keeps coming back. Yeah I know 'its documented' but its
> causing and will continue to cause grief for new users. I made the
> [1] proposal earlier but thats probably still a way off. What
I don't
Gert Driesen wrote:
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, September 13, 2004 7:50 AM
Subject: Re: [Nant-users] Can't
- Original Message -
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, September 13, 2004 7:50 AM
Subject: Re: [Nant-users] Can't overwrite property
ks/property.html for
an example on how to provide a default value for a property and still
allow it to be overridden on the command line.
Hope this helps,
Gert
- Original Message - From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 10, 2004 7:52 PM
Subje
allow it
to be overridden on the command line.
Hope this helps,
Gert
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 10, 2004 7:52 PM
Subject: [Nant-users] Can't overwrite property when readonly not set
I get the followin
I get the following error Read-only property "" cannot be
overwritten. BUT readonly is not set???
Is this a known defect in nant-0.85-20040904
Regards
Dave
The information in this e-mail, and any attachment therei
>From: "Ian MacLean" <[EMAIL PROTECTED]>
>Sent: Friday, August 13, 2004 12:27 AM
> Gary Feldman wrote:
> >>From: "Ian MacLean" <[EMAIL PROTECTED]>
> >>Sent: Thursday, August 12, 2004 6:40 AM
> >>
...
> sorry - I don't buy it. Is
>
> name=value really that much simpler than:
>
>
The former is th
Gary Feldman wrote:
> >From: "Ian MacLean" <[EMAIL PROTECTED]>
> >Sent: Thursday, August 12, 2004 6:40 AM
> >
> > Actually I don't see how adding property files is any
> > different from
> > using the task to import properties. And I don't
> > see how it
>
> There are a number of ways that th
Gary Feldman wrote:
From: "Ian MacLean" <[EMAIL PROTECTED]>
Sent: Thursday, August 12, 2004 6:40 AM
Actually I don't see how adding property files is any different from
using the task to import properties. And I don't see how it
There are a number of ways that the property mechanism in A
>From: "Ian MacLean" <[EMAIL PROTECTED]>
>Sent: Thursday, August 12, 2004 6:40 AM
> Actually I don't see how adding property files is any different from
> using the task to import properties. And I don't see how it
There are a number of ways that the property mechanism in Ant is
different from N
scope would be cause for many random, confusing results rather than hard errors which can be hunted down with ease.
Original Message Follows
From: "Troy Laurin" <[EMAIL PROTECTED]>
To: "Nant-Users (E-mail)" <[EMAIL PROTECTED]>
Subject: Property change-su
I quite like the idea of paramaters. It would solve the current issues
with distinguishing properties defined in the build file from those
passed on the command line as well as add additionaly niceness to
targets. Return values from targets I'm not so sure about.
I tend to agree with Troy that
ttoria wrote:
I like Gary's idea.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gary Feldman
Sent: Wednesday, August 11, 2004 3:11 PM
To: Nant-Users (E-mail)
Subject: Re: Property change-suggestions, was RE: [Nant-users] can't
overwrite prope
Gary McCullough wrote:
> OK, here's my idea NAnt world:
My thoughts on these...
> Scopable properties
> Parameter variables
I'm all over the idea of parameters, it would render utility targets
that are currently property driven much safer, and largely
self-documenting as well - especially if do
> Let me throw out a different idea. Why not add propertyfiles, akin
> to the way they're done in Ant? It's a different approach, but it
> solves many of the same problems.
I may have missed something earlier in this discussion, but property files are already
supported using the task. I use a
I like Gary's idea.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Gary Feldman
Sent: Wednesday, August 11, 2004 3:11 PM
To: Nant-Users (E-mail)
Subject: Re: Property change-suggestions, was RE: [Nant-users] can't
overwrite property
>From
>From: "McCullough, Gary" <[EMAIL PROTECTED]>
>Sent: Wednesday, August 11, 2004 9:30 AM
>OK, here's my idea NAnt world:
>
>Scopable properties
>Parameter variables
>Return values
Let me throw out a different idea. Why not add propertyfiles, akin
to the way they're done in Ant? It's a different
McCullough
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Troy Laurin
Sent: Tuesday, August 10, 2004 11:10 PM
To: Nant-Users (E-mail)
Subject: Property change-suggestions, was RE: [Nant-users] can't
overwrite property
I'm sure people are sick of ge
I'm sure people are sick of getting a slough of mails from me, so I'll
combine these ones :-)
Richard Poole wrote:
> I'm relatively new to NAnt so please forgive me if this is a
rubbish/old idea. :)
>
> --- C# snippet ---
>
> public void MyFunction()
> {
> int a = 2; // const or not
> My reading is that Merrill is saying that the script cannot
> override the command line, but that Ian misinterpreted this
> the other way around, i.e. he thought it means that the
> commandline cannot override the script.
>
> If my reading is correct, then much of the subsequent
> discussi
Thanks. I hope to remember this :)
Felice
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Fre
>>> You cannot unmark a property as being readonly
In other words, readonly is a Very Sticky bit. :-)
Merrill
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for
ECTED]>
Sent: Tuesday, August 10, 2004 2:30 PM
Subject: Re: [Nant-users] can't overwrite property
Well ..
I modified my property statement to this:
When I run: nant /f:test.build -D:junk="Development" or nant
/f:test.build -D:junk=Development I get this:
Read-only propert
>From: "Ian MacLean" <[EMAIL PROTECTED]>
>Sent: Monday, August 09, 2004 9:41 PM
Either I'm confused, or this entire discussion is based upon a
misinterpretation:
> Merrill Cornish wrote:
>
> > Felice,
> >
> > In the new, improved NAnt, properties now have the option of a
> > readonly attirbute.
_
Gary McCullough
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gert
Driesen
Sent: Tuesday, August 10, 2004 2:26 AM
To: Troy Laurin; Ian MacLean
Cc: Nant-Users (E-mail)
Subject: Re: [Nant-users] can't overwrite property
The easiest, an
Well ..
I modified my property statement to this:
When I run: nant /f:test.build -D:junk="Development" or nant /f:test.build
-D:junk=Development I get this:
Read-only property "junk" cannot be overwritten.
I would expect that I can overwrite the property if I set readonly to false and
over
ne).
Gert
- Original Message -
From: "Troy Laurin" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>
Cc: "Nant-Users (E-mail)" <[EMAIL PROTECTED]>
Sent: Tuesday, August 10, 2004 7:27 AM
Subject: RE: [Nant-users] can't overw
Ian Maclean wrote:
> >The previous behaviour of silently ignoring the property task if the
> >property is read-only certainly isn't optimal, either. Silently
> >ignoring tasks can make some bugs hard to trace.
> >
> >
> No quite silently - a message was added to the log - but I
> take your p
Troy Laurin wrote:
Ian MacLean wrote:
Merrill Cornish wrote:
Felice,
In the new, improved NAnt, properties now have the option of a
readonly attirbute. Furthermore, any property set because
it appeared
in a -D:property=value item on the script command line will
automaticall
Ian MacLean wrote:
>
> Merrill Cornish wrote:
>
> > Felice,
> >
> > In the new, improved NAnt, properties now have the option of a
> > readonly attirbute. Furthermore, any property set because
> it appeared
> > in a -D:property=value item on the script command line will
> > automatically be
Merrill Cornish wrote:
Felice,
In the new, improved NAnt, properties now have the option of a
readonly attirbute. Furthermore, any property set because it appeared
in a -D:property=value item on the script command line will
automatically be readonly. So, you can't change in the script the
val
Felice,
In the new, improved NAnt, properties now have the option of a readonly
attirbute. Furthermore, any property set because it appeared in a
-D:property=value item on the script command line will automatically be
readonly. So, you can't change in the script the value of a property passed
Hello all,
I'm using this version of Nant 0.85:
NAnt 0.85 (Build 0.85.1682.0; net-1.0.win32; nightly; 8/9/2004)
I have this test.build file:
When I run: nant
38 matches
Mail list logo
