Question

By specifying “-lib foo.jar” to ant I get the behaviour that the classes in foo.jar is added to the ant classloader and are available for various tasks taking a class name argument.

I’d like to be able to specify the same behaviour but only from inside build.xml (so we can do this on a vanilla ant).

For taskdefs we have functioning code looking like:

<taskdef resource="net/sf/antcontrib/antlib.xml" description="for/foreach tasks">
    <classpath>
        <pathelement location="${active.workspace}/ant-contrib-1.X/lib/ant-contrib.jar" />
    </classpath>
</taskdef>

where the definition is completely provided from the ant-contrib.jar listed.

What is the equivalent mechanism for the “global” ant classpath?

(I have thought out that this is the way to get <javac> use ecj-3.5.jar to compile with on a JRE – Specifying the Eclipse compiler completely from _within_ build.xml – in a way compatible with ant 1.7. Better suggestions are welcome 🙂

---

EDIT: It appears that the about-to-be-released version 1.0 of ant4eclipse includes ecj. This does not answer the question, but may solve my basic problem.

Answer 1

if you ever decide to move to Ant 1.8 you can use following construction:

<import>
  <javaresource name="resource_name.xml">
   <classpath location="path_to_jar.jar" />
  </javaresource>
</import>