I don't know if it's the right way to do it, or if there is some reason not to do it this way, but I found a solution... I took the contents of the target that executed Antform and put it in a macrodef... doing that, the properties DO get changed as expected.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] On Tue, February 14, 2006 12:09 pm, [EMAIL PROTECTED] said: >>Now, within that target, the properties are set according to >>what I do on the form (and matches the properties file written >>at that point). >>However, in a later target, the value of a given property is >>the value that was in the file BEFORE Antform rewrote it, >>i.e., it is the value is started out as when the script ran. > > Properties are immutable! > > >>So, I need a way to tell Ant to reload that properties file >>and update the values accordingly. > > Ant wont. > You could reload them with another name using > <property prefix/> > > >>Alternatively, I need a >>way for the property values set in the one task to replicate >>to the rest of the script (some sort of scoping issue, but I'm >>not sure how to deal with it). > > properties are valid for the whole project. > There is only a difference when using <ant>,<subant>,<antcall>. > > > Jan > > --------------------------------------------------------------------- > 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]
