On Mon, 25 Feb 2002 03:18, [EMAIL PROTECTED] wrote: > On Sun, 24 Feb 2002, Peter Donald wrote: > > > > Use of a separate instance of ClassLoader for each task instance. So > > > > ideally if you run velocity twice then separate ClassLoaders will be > > > > created for each run. This is because some tasks use static variables > > > > through dependent libraries. > > > > > > So, do you want in ANT that each use of each task be with a separate > > > ClassLoader? That should really break everything, don't you think? > > > > No more than separate ClassLoaders for each library. > > A separate ClassLoader for each external taskdef is what ant1.4 does > ( check <taskdef> ). > > A separate ClassLoader for each Task will brake inter-task communication,
no more than "ClassLoader for each external taskdef" or a "ClassLoader for each library" > among other things. Maybe running each target in a different > class loader, but even that is too much ( I may agree with running each > <ant> call in a different class loader ). eww. Separate ClassLoader for target or per project? > 'Static variables' are an important and usefull feature, > separate ClassLoader per task would brake this as well. heh. I think they suck and leaf to several uglies hacks ... heres one of them. -- Cheers, Pete --------------------------------- I think not; therefore I ain't... --------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
