Gert Driesen wrote:
----- Original Message -----
From: "Ian MacLean" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, September 24, 2004 10:36 AM
Subject: Re: [Nant-users] RE: can"t overwrite property
the consensus right now is that the param solution is probably the best
way to go but it will be more than a quick hack and probably won't make
the next release.
I'm still not sure it really is the best way to go, as we need to be able to
execute (quite) some logic (meaning tasks, targets and/or functions) in
order to determine the default value of a given property.
you mentioned this before but didn't actually explain why this is
required. Maybe I'm missing somthing
The <param> construct as proposed, does not allow this. We'll definitely
need to give this more thought.
sure and regular <property> s don't allow this either - why do we need
to be able to do this ?
As I've said previously I'm almost in favour of
reverting to the previous behaviour until we have a clean solution in
place. Its seeming like the user confusion around this issue is
outweighing the benefits of correctly throw the exception when
overwriting readonly properties.
Ian, for now we might just output a warning instead of having the build
fail.
Sounds good to me.
Ian
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
