On Thu, 18 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]> wrote: > Since Costin has not chimed in, it is worth reading this message and > Costin's followup
Interesting, you are raising the same point as me 8-) The situation could be "fixed", if AntClassLoader would know whether it has loaded any class/resource - and <classloader> would only work on instances that haven't loaded anything yet. This would take away the power to modify the core loader, of course - but since the core loader doesn't have to be an AntClassLoader instance and never is AFAICS, the task wouldn't work on that anyway. The task as is may be useful to some but will cause more problems that good for the uninitiated - thus I'd rather not like to see it in Ant's core distribution. There is nothing in that task that would make it unusable if it came from a different jar/antlib. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
