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 4884] - Dependant targets fire unnecessarily
Date Thu, 15 Nov 2001 19:11:17 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4884>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4884

Dependant targets fire unnecessarily

tgochenour@peregrine.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From tgochenour@peregrine.com  2001-11-15 11:11 -------
The scenario you give will continue to work with my enhancement request.  The 
only possible break with backward compatibility is when "property.is.set" is 
ALREADY SET yet the author still wants dependent targets to fire.  Are there 
any actual instances where when the primary target is already known to be 
invalid yet the user still wants the dependent targets to fire?

There are scenarios, however, where I want the entire set of targets to be 
invalid, for no other reason than to optimize performance.

The if and unless conditions should be checked both before and after the firing 
of dependents.  I believe this change will be safe for all existing ant 
implementations.

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


Mime
View raw message