In the Advanced Tab you can specify advanced options for the transformation.
You have several parameters that you can specify here:
If you use a custom DITA-OT build file you can specify the path to the
customized build file. If empty, the build.xml
file from
the dita.dir
directory configured in the
Parameters tab will be used.
You can specify a build target to the build file. By default no target is necessary and the default "init" target is used.
You can specify additional command line arguments to be passed to the ANT
transformation like -verbose
.
You can specify a custom ANT installation to run the DITA Map transformation. By default it is the ANT installation bundled with <oXygen/>.
You can specify a custom Java Virtual Machine to run the ANT transformation. By default it is the Java Virtual Machine used by <oXygen/>.
This parameter allows you to set specific parameters to the Java Virtual
Machine used by ANT. By default it is set to -Xmx256m
which
means the transformation process is allowed to use 256 megabytes of memory.
Example 6.1. Increasing the memory for the ANT process
Sometimes, when performing a large DITA map transformation you may want to increase the memory allocated to the Java Virtual Machine from the default value (64 MB) to a higher value (256MB). You can do this easily by setting the value '-Xmx256m' without quotes to the "JVM Arguments" text field. In this way you can avoid the Out of Memory ( OutOfMemoryError ) messages received from the ANT process.
Oxygen adds by default as high priority libraries which are not transformation-dependent and also patches for certain DITA Open Toolkit bugs. You can specify all the additional libraries (jar files or additional class paths) which will be used by the ANT transformer. You can also decide to control all libraries added to the classpath.
Example 6.2. Additional jars specified for XHTML
For example the additional jars specified for XHTML are the DITA-OT dost and resolver jars, xerces and saxon 6 jars.