On Sat, Jan 06, 2007 at 02:48:52AM +0100, Christian Geisert wrote:
Simon Pepping schrieb:
According to the documentation page fop may be run as:
java -jar build/fop.jar.
In our own bin packages that does not work, because the manifest file
lists the libraries without a path. Does
available.
On 06.01.2007 11:06:08 Simon Pepping wrote:
On Sat, Jan 06, 2007 at 02:48:52AM +0100, Christian Geisert wrote:
Simon Pepping schrieb:
According to the documentation page fop may be run as:
java -jar build/fop.jar.
In our own bin packages that does not work, because
On Sat, Jan 06, 2007 at 11:40:27AM +0100, Jeremias Maerki wrote:
One thing we could try is to pass in FOP's home directory through a
system property so cli.Main has a better chance of building the right
classpath when the batch file is not called from FOP's home directory.
Something like:
According to the documentation page fop may be run as:
java -jar build/fop.jar.
In our own bin packages that does not work, because the manifest file
lists the libraries without a path. Does that have a special reason?
I think it would be better to change it to ../lib/xxx.jar.
I also would like
