Adding a Java library to the classpath
You can use the dita.conductor.lib.import
extension point to add an additional Java
library to the DITA-OT classpath parameter.
About this task
As of DITA-OT 3.1, the Java class path is managed automatically, meaning you do not (and should not) use
explicit references to Java class paths in your build scripts. In particular, the old
dost.class.path
property has been deprecated and should not be used. If you are migrating
older plug-ins that manage their class path directly, you should remove any explicit class path configuration.
If your plug-in was not already using the dita.conductor.lib.import
extension point to
integrate its JAR dependencies you must add it.
The effective DITA-OT class path is the combination of the JAR files in the main lib/ directory and the plug-in-contributed JARs, which are listed in config/env.sh. The env.sh file is updated automatically when plug-ins are installed or removed.
Procedure
Results
Example
In the following extended example, the myJavaLibrary.jar file performs a validation step
during processing, and you want it to run immediately before the conref
step.
To accomplish this, you will need to use several features:
- The JAR file must be added to the classpath.
- The Ant target must be added to the dependency chain for conref.
- An Ant target must be created that uses this class, and integrated into the code.
The files might look like the following: