I'm no expert and I don't know if it'd cause the problems you're seeing but
the definition of your classpath doesn't look right.
Using <include name="**/*" /> will include all files below the ${build}
directory. Do you perhaps only want to include the build directory itself?
E.g.
<path id="classpath">
<pathelement path="${build}"/>
<fileset dir="${build}">
<include name="*.jar" />
</fileset>
</path>
Also if you haven't done a ant clean the <include name="*.jar" /> will pick
up mining.jar from a previous build.
Cheers,
Tobin.
> -----Original Message-----
> From: Tara Hernandez [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 23, 2002 10:23
> To: Ant Users List
> Subject: Re: Question about ant performance
>
>
> Yes. Our product is fairly obscene. I'm trying some of the
> suggestions
> mentioned to see what happens.
>
> And due to the many questions about what other targets look
> like, I've attached
> the whole build.xml file for anyone who's curious. Also, my
> ${src} dir looks
> like this:
>
> src/com/comp/pack1
> /pack2
> /pack3 <--- most of the files live in one dir
>
> -Tara
>
> Dominique Devienne wrote:
>
> > And you're old GNU make stuff, did it also include that
> many third party
> > JARs?
>
> --
> "I was gratified to be able to answer promptly, and I did. I
> said I didn't
> know"
>
> -Mark Twain
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
