> -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Monday, July 24, 2000 5:29 AM > To: [EMAIL PROTECTED] > Subject: Re: [PATCH] Minor fix for bug in Property task > > > >>>>> "PP" == Paul Philion <[EMAIL PROTECTED]> writes: > > PP> And speaking if immutable properties, doesn't this check belong > PP> in Project.setProperty? > > Yes, if we wanted to keep them immutable. Right now they are immutable > in a sense that you cannot change them with <property> tasks, that's > all. > > From the recent discussion I'd expect the semantics of properties to > change (again). >
I hate overloading tasks with so many flags that you need a new manual just to understand the side effects you can make. Why don't we add (the people clammoring for mutable tasks) a new task <mutate property="abc" value="newXYZ value"> That would solve the problem and stop overloading the meaning of <property>. Even for <ant> and <calltarget> I would suggest we rename their <properties> inner entities to <param> or <paramproperty> which is what those values are. I really think that part of the problem is that we are overloading the usage of <property> too much and now people want to use it as the way to dealt with everything. Jose Alberto
