ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Murdoch" <>
Subject RE: cvs commit: jakarta-ant/proposal/myrmidon/src/todo/org/apache/tools/todo/types
Date Wed, 27 Mar 2002 10:13:40 GMT

> -----Original Message-----
> From: Peter Donald []
> Sent: Wednesday, 27 March 2002 5:39 PM
> To: Ant Developers List
> Subject: Re: cvs commit:
> jakarta-ant/proposal/myrmidon/src/todo/org/apache/tools/todo/types
> On Wed, 27 Mar 2002 18:04, wrote:
> >   * Moved responsibility for creation of ClassLoaders out of 
> the tasks, and
> > into the ClassLoaderManager, which caches them, and resolves extension
> > dependencies.
> Are you sure caching is a good idea? Personally silent caching is 
> going to be 
> very counter-intuitive to me and as it is in the innerts of 
> ClassLoaderManager it would not be possible to overide. 
> Thoughts?

I agree.  This is just a first pass - I used the ClassLoaderManager because doing so happened
to pick up some useful stuff, like reusing the classloader, including the common classloader
as parent (as opposed to the now empty system classloader), and resolving extensions.  But
we do want to make all of these things configurable.  Sometimes you want to reuse a classloader,
sometimes you want to spin up a new one for every object instance.  Sometimes you want to
include the common classloader, sometimes you don't.  And so on.

Eventually, I want to add a data-type that represents a classloader, and gives the user control
over all this stuff.  This makes things like reuse explicit - use a classloader data-type
by ref, and you reuse the classloader, and so on.  This would also tie in with the ExtensionManager,
so that you can use, for example, the classloader or classpath for a particular extension
(, for example).


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message