To produce this document we used an Ant build script containing targets for building all transformation types (often called "transtypes" or "targets") supported by DITA Open Toolkit. The location of the Toolkit, the location of the source files, and the location of the output files are variables that can be changed. These lines at the beginning of the script show how this is done:
<?xml version="1.0" encoding="UTF-8" ?>
<!-- (c) Copyright IBM Corp. 2004, 2005 All Rights Reserved. -->
<project name="toolkitug" default="all" basedir="C:/ditaot">
<!-- Location of project working files -->
<property name="projdir" value="C:/DITAOT_UGRef_SOURCE"/>
<property name="outdir" value="C:/DITAOT_UGRef_OUTPUT"/>
<property name="args.logdir" value="${outdir}"/>
In the Windows operating environment we built to all transtypes to make sure they would build cleanly. On Linux, we tested XHTML output only.
We use a Windows batch file (runbuild.bat) to initiate the build. The batch file calls the DITA Ant logger that types a summary of build progress on the console (rather than a more verbose set of messages) and uses a log file to capture the details. Here is our batch file:
ant -f ant_scripts\DITAOT_UGRef_all.xml -logger org.dita.dost.log.DITAOTBuildLogger %1
This method gives us enough information on the console screen to tell whether or not the build was successful and whether any errors occurred that need immediate attention.