Custom if/unless attributes in Ant scripts
Ant scripts for DITA-OT builds now make use of if:set and unless:set
attributes in the Ant namespace, which can be used to control whether parameters are passed to XSLT modules.
These attributes replace custom implementations of if and unless logic
introduced before Ant had this capability.
If your plug-ins include Ant scripts that use if or unless on
param elements that pass XSLT parameters, add the following namespace attributes to
the root project:
- xmlns:if="ant:if"
- xmlns:unless="ant:unless"
In custom Ant build files and in any files that supply parameters to existing DITA-OT XSLT modules, replace all
occurrences of if="property" on param elements with
if:set="property" (and unless → unless:set
respectively).
<root xmlns:if="ant:if" xmlns:unless="ant:unless">
<param name="antProperty" expression="${antProperty}"
if:set="antProperty"/>
</root>
For more information on passing parameters to existing XSLT steps, see
.
Deprecated properties
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.
The xml.catalog.files property has been deprecated and should not be used. Replace any such
references with the xml.catalog.path instead.