Hi,
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.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
|