On 12/27/06, Gilbert Rebhan <[EMAIL PROTECTED]> wrote:
Hi, [EMAIL PROTECTED] wrote: > Comment" on jGuru [2]. Comments on jGuru are welcome. hope it's OK to Cc: my post here, as some people might have only connection to the ant-user list @ work !? following my post on jGuru = /* Hi, the immutable properties are no problem for me, using ant for 4 years now, i'm used to it. I know i can get over it easily via <script> task and project.setProperty ... IMO it's good that properties are immutable by default. And if i would need it other than that, i could use the <variable> task from antcontrib. Regards, Gilbert */ Regards, Gilbert
My comment to the blog was: """My opinion is that immutable properties happened by accident, and have been kept in ant for a number of reasons, some good and some bad. The main "good" reason is that ant strives to be backward compatible for each release. Any non backward compatible change *will* affect scripts in production. This "good" reason is also a bad reason in that it keeps bad decisions forever and many aspects of the design of properties and their sibling "references" are strange and twisted. The user, "special" and basedir properties have been the cause of many bugs and scratching of heads over the years. As regards "antcontrib:var", initially when I saw the unset feature (and it's implementation), I though whatthe** is this? Later on I realized that it is actually a good thing to do, so there will be some support in ant for var in the near future.""" Peter
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
