On Fri, 24 May 2002 09:23, [EMAIL PROTECTED] wrote: > The big question is - can we agree to make the default > behavior 'reuse' - i.e. taskdef will allways use the same > loader for the same classpath ? If we do, then I can remove > the magic property and the attribute. Is it possible that someone is > actually using the fact that <taskdef> will create a different class > loader for each task ? I think it is a bug, but if it is considered a > feature we'll have to preserve it.
It is a feature not a bug unfortunately ;( Some people who have written tasks that use statics used to re taskdef tasks to get a "clean" task prior to each invocation. However I am not sure this works anymore because of changes that Stefan made wrt overiding tasks etc? I dunno - Stefan ? -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
