ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Kjome <h...@visi.com>
Subject macrodef and properties
Date Fri, 14 Nov 2003 05:28:45 GMT

I have a macrodef where It does some work, then does a <pathconvert> which 
stores the result in a property, then something else uses that property 
value.   When I make calls to this, the first call works fine, but 
subsequent calls use the previously set property which, apparently, is set 
globally in the build.  This isn't very useful at all.  Is this going to be 
changed.  I saw the following conversations, but I'm not completely sure if 
the issues raised/fixed there affect my issue...

http://issues.apache.org/bugzilla/show_bug.cgi?id=23942
http://marc.theaimsgroup.com/?l=ant-dev&m=106664032815130&w=2
http://marc.theaimsgroup.com/?l=ant-user&m=106674668723133&w=2

Will the stuff in bug 23942 solve my issue?  If so, when is this patch 
going to be applied?  I'm using the latest 1.6 CVS.  Is my only workaround 
using <antcall>?  Wasn't the whole point of <macrodef> to get rid of the 
necessity for <antcall>?

Jake


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message