You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2004/01/15 11:32:48 UTC

DO NOT REPLY [Bug 26160] - taskdef could not load definitions from resource

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26160>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26160

taskdef could not load definitions from resource





------- Additional Comments From peter.reilly@corvil.com  2004-01-15 10:32 -------
Classpath handling has changed in 1.6.0.
It seems that the resource is searched for in the classloader
generated from the classpath setting and not in the parent classloader.

Please note that
<taskdef classpath="jcoverage.jar" resource="tasks.properties"/>
will look for tasks.properties in ${basedir}/jcoverage.jar and
(in 1.5.5) in the ${ant.home}/lib/*.jar, so as jcoverage.jar in
${ant.home}/lib in your example, the classpath attribute is
not necessary and is confusing.
so use:
<taskdef resource="tasks.properties"/>

Also note that if "tasks.properties" is in another other jar
file in ${ant.home}/lib, your taskdef will fail.
A work-around for this would be to do as you say:

<taskdef classpath="${ant.home}/lib/jcoverage.jar" resource="tasks.properties"/>
which should work in 1.5.4 and 1.6.0.

I am leaving this open as the resource should have been found (I think).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org