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=9675>. 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=9675 Custom tasks can be run in an unconfigured state [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From [EMAIL PROTECTED] 2002-06-07 00:32 ------- I've tracked this down to the maybeConfigure method in RuntimeConfigurable. The statement attributes = null means the RuntimeConfigurable cannot be reused. When the task is invalidated by the second taskdef, the new instance needs to be configured from the same RuntimeConfigurable. I'm not sure of the motivation for setting to null and what other impacts not setting it to null may have. Obviously the statement characters.setLength(0); is also a problem. Commenting these out allows your build to run OK. It does not appear that the child list is nulled out though. Want to test with a nested element? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
