In the Advanced tab, you can specify advanced options for the
transformation.
Advanced settings tab
You have several parameters that you can specify here:
Custom build file - 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 is used.
Build target - You can specify a build target to the build file. By
default no target is necessary and the default init target is used.
Additional arguments - You can specify additional command-line
arguments to be passed to the ANT transformation like -verbose.
Ant Home - You can specify a custom ANT installation to run the
DITA Map transformation. By default it is the ANT installation bundled with Oxygen.
Java Home - You can specify a custom Java Virtual Machine to run
the ANT transformation. By default it is the Java Virtual Machine used by Oxygen.
JVM Arguments - 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. 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 (256 MB)
to a higher value, like 512 MB. In this way, you can avoid the Out of Memory error messages
received from the ANT process.
Note: If you are publishing DITA to PDF and still experience
problems, you should also increase the amount of memory allocated to the FO transformer.
To do this, open the Parameters tab and increase the value of
maxJavaMemory parameter (default value is 500).
Libraries - 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 are used by the ANT transformer. You can also decide to control all
libraries added to the classpath.