> There are two reasons for wanting tasklibs and different classloaders: > (1) You want to have a way to say: this sub-build requires such and such support > > without needing to know it globally, which is required when using the > classpath.
Hmmm. I don't know if we want to scope this sort of thing at the target level. I think it's a property of the project. > > (2) After we have lots of people contributing lots of stuff, you want to be able > to > isolate the libraries apart to avoid any nasty conflict, except for the ANT > core which > lives in the CLASSPATH, each library can use its own stuff. That's a good point. > Additionally, having libraries may allow things like the library declaring its > own tasks, > so like core, the action of defining the library declares its tasks implicitly. > This is a > little more of work, but should not be difficult if we use XML :-) > > If I ever get some time I'll try to work on it. I'm in the process of gathering design notes... I'll spend some time looking at this in the scope of things and see how it fits together. .duncan
