----- Original Message -----
From: "Stefan Bodewig" <[EMAIL PROTECTED]>
Sent: Friday, December 07, 2001 3:08 AM
> > Immutable properties are good because they free ant developers and
> > ant users from worrying about sequencing concerns in project
> > processing and it is a much simpler model for build file
> > writers.
>
> I think you are mixing properties being made immutable by the core and
> properties being immutable by the choice of the tasks.
>
> Look at what I've changed with my commit - log messages and comments
> and I removed a @deprecated tag. I'm not against modifying our
> current tasks so that they keep properties immutable, I just want to
> make sure that task writers have the choice to do different in their
> own tasks.
I'm "ok" with how you've modified things.... I'd be even happier if
<available>'s hole was closed so that truly the core tasks kept things
immutable, but for the sake of backwards compatibility I guess I'll just
have suffer through it. :)
> Build file writers won't have to worry about sequencing or anything
> else, as long as they don't use their own <change-property> task.
Or <available>.
> The built-in tasks we have are as consitent when it comes to treating
> properties as they've been two hours ago.
Agreed.
Erik
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
