|
From: Andreas M. <ma...@in...> - 2004-05-26 14:35:04
|
Hi Joerg,
On Wed, May 26, 2004 at 02:49:42PM +0200, Joerg K. Wegner wrote:
> 1. append all required *.jar files to the CLASSPATH environment (not
> recommended)
Not knowing the setup of potential users I could only do this on my own system.
=> I won't do it.
> 2. use ant and catch all *.jar files to build a 'local' classpath for
> your program
sounds good. Does this mean to create an .xml file having a target that launches my .class file
provided with the information where it can find the bib?
Can I do this with something like:
...
<classpath>
<fileset dir="${lib}">
<include name="**/*.jar" />
</fileset>
</classpath>
...
Of course, additionally I would have to search the joelib-tree recursively to catch all jars. Do you know a good knowledge resource on the web about ant?
> 3. use shell/batch script to build a 'local' classpath for your program
> (you can use one of JOELib's as base). But under windows this is not a
> good solution, because all dependencies are hard-coded.
> So i recommend ant or shell-scripts using cygwin.
Don't know exactly what this means. What do you mean by "'local' classpath"?
You don't speak of the environment variable $CLASSPATH, do you?
Greets,
Andreas
|