Home/ Questions/Q 709095
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T04:27:56+00:00

When declaring external ant tasks using taskdef, for instance ant-contrib, the proposed setup is

  • 0

When declaring external ant tasks using taskdef, for instance ant-contrib, the proposed setup is to use the followin taskdef:

<taskdef resource="net/sf/antcontrib/antcontrib.properties">
  <classpath>
    <pathelement location="lib/ant-contrib/ant-contrib-1.0b3.jar"/>
  </classpath>
</taskdef>

This works when antcontrib.properties is located in net/sf/antcontrib relative to the build.xml file.

But when I put it in lib/net/sf/antcontrib and changes the taskdef into

<taskdef resource="lib/net/sf/antcontrib/antcontrib.properties">
  <classpath>
    <pathelement location="lib/ant-contrib/ant-contrib-1.0b3.jar"/>
  </classpath>
</taskdef>

Ant is not able to find the properties file, it gives the error

[taskdef] Could not load definitions from resource
lib/net/sf/antcontrib/antcontrib.properties. It could not be found.

It seems like ant treats the lib directory separately and fails to load a taskdef resource from there.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As Alex said, you shouldn’t need to unzip the jar. The <taskdef> can load antcontrib.properties directly out of the jar.

    The error you got is because you changed the resource path, but the path to the file inside the compressed jar/zip is still the same. The taskdef isn’t paying attention to the properties file you moved because the <classpath> you provided to <taskdef> tells it to only look in the jar.

    • 0