On Wed, 17 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote: [Stefan writes story about classes being loaded multiple times by the same classloader but via different paths]
> Yikes! To be fair, I should add that the <classloader> implementation doesn't work for class loaders that are not AntClassLoaders, so you won't be able to manipulate the system classloader - but the issues would be the same. > I have done some more investigation. The reason why using defined > definitions do not work unless antlib is an taskcontainer is > UnknownElement#handleChildren. This loops tru the all unknown > elements and checks if the parent can handle them. After > handleChildren is called, the maybeConfigure is called which invokes > the defines if addConfigured(AntlibInterface) is used in antLib. So you need to supress/delay the invocation? I'm not sure I follow you, sorry. > A fix could be to keep antlib being a task container, but check > if the type of task/type is a AntlibInterface, and if not, to > reject the task/type. I don't think so. To me it seems that it should be possible for <antlib> to accept arbitrary AntlibInterface instances as children without resorting to TaskContainer. If Antlib can't do that, it feels as if something was not right ATM. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
