ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Ant changes breaking Axis
Date Wed, 08 Jan 2003 11:23:13 GMT
On Tue, 7 Jan 2003, Steve Loughran <> wrote:

> Whatever has happened to Ant recently has broken Axis

At first glance, it seems to be a Gump problem.

The exception happens when the reference to the <path> named
"classpath" defined in axis/java/xmls/path_refs.xml gets expanded
inside the <taskdef> from axis/java/xmls/taskdefs_post_compile.xml
that is included in axis/java/samples/transport/build.xml, which in
turn has been called by <ant> from axis/java/buildTest.xml.

You sure know how to complicate builds ;-)

Gump invokes Ant with -Dlib.dir=lib which then overrides the
definition in properties.xml (that would point to ${axis.home}/lib
using the absolute path).

This in turn means that this part

    <fileset dir="${lib.dir}">
        <include name="**/*.jar"/>

of path_refs.xml now is "lib" relative to the basedir of the build
file - in build.xml it is axis/java/samples/transport/lib.  The
problem we see.

The "Caught exception" message comes from the <path> included, it
doesn't hurt too much.

The build failure happens, when the path gets used in the first
taskdef from taskdefs_post_compile.

After this analysis, -Dlib.dir=lib looks the problem and has been
introduced a month ago [1].  I'd be content and happy, but then again
- it gets built successfully in my Gump environment that uses the 1.5
branch of Ant.  Honestly, I don't know why 8-)

I'll investigate further, but thought I'd share what I've found so


[1]  <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message