From 2198b4395c27f3ba3fa6688e316eb246c5c08e73 Mon Sep 17 00:00:00 2001
From: Simon Pepping
Date: Sat, 6 Jan 2007 11:07:37 +0000
Subject: [PATCH] Added to the documentation of FOP's classpath and jar
features
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@493445 13f79535-47bb-0310-9956-ffa450edef68
---
.../content/xdocs/trunk/running.xml | 126 ++++++++++++------
1 file changed, 85 insertions(+), 41 deletions(-)
diff --git a/src/documentation/content/xdocs/trunk/running.xml b/src/documentation/content/xdocs/trunk/running.xml
index ec82feb72..4b488ef12 100644
--- a/src/documentation/content/xdocs/trunk/running.xml
+++ b/src/documentation/content/xdocs/trunk/running.xml
@@ -105,60 +105,73 @@
PDF encryption is only available if FOP was compiled with encryption support
@@ -177,12 +190,43 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl
the standard scripts to make sure that
you get your environment properly configured.
+
+
+ Running with java's -jar option
- As an alternative to the start scripts you can run "java -jar build/fop.jar" in which case
- FOP tries to build the classpath for running FOP dynamically. Please note, that this might
- not always work as expected.
+ As an alternative to the start scripts you can run java
+ -jar build/fop.jar from the FOP_HOME directory. In this
+ case FOP tries to build the classpath for running FOP
+ dynamically, see below. If
+ you use hyphenation, you must put fop-hyph.jar in
+ the lib directory.
+
You can also run java -jar fop.jar from any
+ other working directory. This only works if you put
+ fop.jar and all jar files from the lib
+ directory in a single directory. See the Class-Path
+ entry in the manifest file. If you use hyphenation, you
+ must also put fop-hyph.jar in that directory.
+
+ FOP's dynamical classpath construction
+
+
If FOP is started without a proper classpath, it tries to
+ add its dependencies dynamically. FOP expects to find
+ fop.jar in the build directory,
+ which is either the current working directory or one of its
+ subdirectories. Then FOP adds all jar files in
+ the lib directory to the classpath. The
+ lib directory is a sibling directory of the
+ build directory, or, if that does not exist, the
+ parent directory of the build directory. If the
+ system property fop.optional.lib contains the
+ name of a directory, then all jar files in that
+ directory are also added to the classpath. See the methods
+ getJARList and checkDependencies in
+ org.apache.fop.cli.Main.