ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject new Launcher and <taskdef>
Date Thu, 10 Jul 2003 13:56:21 GMT

the new Launcher introduces the well known fun of delegating
classloaders to <taskdef>, only this time it's the other way around.

If you use <taskdef classname="org.example.Foo"/> and Foo is on the
system classloader, but ant.jar is not, <taskdef> will fail as it
cannot load oat.ant.Task.

This used to work as long as all contents of ANT_HOME/lib ended up on
the system classloader, but now it fails.

There is no difference if Foo comes from a jar in ANT_HOME/lib, only
if it is in CLASSPATH.


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

View raw message