ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33956] - Ant target using both 'depends' and 'if'
Date Sun, 13 Mar 2005 09:00:14 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33956>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33956





------- Additional Comments From aps_jobs_aps@yahoo.com  2005-03-13 10:00 -------
(In reply to comment #3)
> If your structure was working before with antcalls it may prove to be more
> beneficial to you to keep depends/if/unless target attributes mostly as-is 
and
> convert your antcalls to macro invocations.  The main reason to "try and 
reduce
> the number of antcalls" is to avoid the cost in memory and time incurred in
> creating the new project instance that goes along with an antcall.  Macrodefs
> achieve this.


I have used macrodefs in place of antcalls in many places to improve 
performance. But it doesnt work quite well in the scenario that I have 
described. Even, if I make targets 2, 3 and 4 as macrodefs and invoke them 
from 1, I still want 4 (which is now a macrodef and not a target) to be 
executed conditionally. And macrodefs do not support conditions and there 
begins the problem. Effectively I am looking at something like this..

<target name="1" if="condition1" >

 <macro 2 />
 <macro 3 />
 <!-- <macro 4 if="condition2" />

</target>

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message