On Mon, 10 Jun 2002, Dominique Devienne <[EMAIL PROTECTED]> wrote: > But isn't this a bug Stefan!?!?!
I don't think so. The second <taskdef> will be loaded via a different classloader. Some people use static information or Singleton like stuff to hold state in the tasks and they will want to know what's going on. In general people will probably want to know when they override an existing taskdef with a different one. You won't get the message if you use the same classloader in all taskdefs, which can be achieved with 1.5beta2's new loaderref attribute. We might decrease the logging level to verbose output only if the classes are different but the class names are the same (i.e. the tasks only differ in the classloader being used). Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
