ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: class.forName()
Date Wed, 21 Nov 2001 08:10:58 GMT
On Mon, 19 Nov 2001, Don Taylor <donald_l_taylor_jr@yahoo.com> wrote:

> --- Stefan Bodewig <bodewig@apache.org> wrote:
> 
> <snip>
>  
>> Everything you have in your CLASSPATH or in ANT_HOME/lib will end
>> up in your system classloader when you run Ant.  If your task
>> implementation can be loaded via this classloader, it *will* be
>> loaded via this classloader, no matter what.  If this task now
>> needs a class from a library that is not in your classpath, it
>> won't find it (as the classloader used to load your task doesn't
>> know about these libraries).
> 
> This is true, but when you declare your taskdef you can embed a
> classpath element within your taskdef to put these libraries into
> your classpath.

The key point here is, that your task definition must not be available
from the system classloader - or your custom classpath in the taskdef
will not be used.  This is what I wanted to say above.

Stefan

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message