2. Classloader improvements. I would like to use a different startup procedure, and allow the use of a class loader hierarchy similar with what tomcat is using. In particular, the startup should be done with empty classpath, and the bootstrap should scan the lib directory. Obviously, this can be configurable. In particular it should be possible to keep the ant runtime in a separate loader, and to add paths to the 'core loader' at runtime.
This would solve the junit.jar issues, and much more, and will be 99% backward compatible. The only breakage will be if classes are using the system class loader directly - those will have to be in the parent loader.
This will break almost all the custom tasks I have written and probably alot of other peoples tasks if they create their own classloaders.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
