ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@bost.de>
Subject Re: setting properties from a User defined Task.
Date Fri, 04 Aug 2000 15:38:08 GMT
>>>>> "KB" == KC Baltz <KBaltz@responsenetworks.com> writes:

 KB> I also call project.setProperty().

If you do this from a task, it will work - but it will have no effect
on the ${} Conor has been talking about, as this substitution happens
at parser time.

If you want to retrieve the value again, you'd need to call
Project.getProperty at task runtime - which you can do in a custom
task (<script> for example) 

 KB> With the new switch to immutable properties, is it now considered
 KB> bad/wrong behavior for a custom task to set a property?

No, not really. "immutable" is probably the wrong word, "not mutable
by subsequent <property> constructs" would be better. And even that
might be dropped again.

Stefan

Mime
View raw message