I found that on Sun Unix I had to explicitly list jar files(not quite the
same method as below) that were in a different place which did not appear
necessary on windows!??
-----Original Message-----
From: Son of Mojo JoJo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 5:27 PM
To: [EMAIL PROTECTED]
Subject: Re: adding manifest entries
is this to compile your jars? the way i did this was pass a string with with
a :
seperated list of external jars to add to the classpath the code looks like
such:
<property name="external.classpath"
value="${built}/${external}/some-jar-youneed.jar:${built}/${external}/some-o
ther-jar.jar"/>
then the compile target has a line like such
<javac srcdir="${src}/${package}" destdir="${built}"
classpath="${external.classpath}" />
"G.L. Grobe" wrote:
> I've got an EJB app that creates jar files, and the classes in these
> jarfiles depend upon a third party jar. Yet my app can't find the classes
in
> this jar. I have nothing in my MANIFEST.mf files (the ones created by
Ant).
> So how do I tell Ant to add the classpath for 3rd party jarfiles I'm
adding?
> If I create a MANIFEST.mf, it just get's ignored by Ant.
>
> Any help much appreciated.
--
-Raphael
[EMAIL PROTECTED]
******************
ook ook im a monkeeeey wheeeeeeee!
********************
