The 1.6 classloader uses the "core" classloader of project. The core classloader was an attempt to set the classloader for loading tasks in an early alpha 1.6 ant development cycle - it did not work and was not used and was never removed from the code base.
A simple classloader extender may be a better task for core ant that the proposed solution, I know that a number of projects use something similar, so it is a pretty common use case. The classpath report task is also very very useful. Peter On 8/25/06, Conor MacNeill <[EMAIL PROTECTED]> wrote:
I'm +1 on having the classloader task and being able to add paths to the main Ant classloader. Internally, we have been using a very simple task to extend the classpath and it is a very elegant solution for users who don't want to modify their ant install, etc. It is not without its hazards but those can be documented and are outweighed by the benefits. Peter, perhaps you could explain why the current task does not work. I must admit the proposal seemed quite complicated. Conor Peter Reilly wrote: > The one in 1.6 does not work. > The proposed one is totally different. > see http://enitsys.sourceforge.net/ant-classloadertask/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
