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 12820] - inheritRefs is broken
Date Wed, 25 Sep 2002 16:30:22 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=12820>.
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=12820

inheritRefs is broken





------- Additional Comments From bodewig@apache.org  2002-09-25 16:30 -------
Is not set to null, but to an "unconfigured" instance.  Unconfigured means
that the attribute setters have not been called.

I know this sounds wrong, but that is the way Ant has been instantiating tasks
and data-types ever since.  Some things depend on references being available
even if the corresponding targets have not been called (see the second example
in <script>'s documentation).

This is the reason why I didn't even bother to implement inheritrefs for <antcall>
in the first version (it will inherit nothing, as everything has been defined
already).  But this is not a bug, but a feature of Ant.

--
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