se/SE/stuff/dita-ot-2.3.3/docsrc/user-guide/using-dita-properties-file.dita

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA General Task//EN" "generalTask.dtd">
<!--This file is part of the DITA Open Toolkit project. See the accompanying LICENSE.md file for applicable licenses.-->

<task id="using-dita-properties-file">
  <title>Setting build parameters with <filepath>.properties</filepath> files</title>
  <shortdesc>Usually, DITA builds require setting a number of parameters that do not change frequently. You can
    reference a set of build parameters defined in a <filepath>.properties</filepath> file when building output with the
      <cmdname>dita</cmdname> command. If needed, you can override any parameter by specifying it explicitly as an
    argument to the <cmdname>dita</cmdname> command.</shortdesc>
  <taskbody>
    <section>
      <title>About <filepath>.properties</filepath> files</title>
      <p>A <filepath>.properties</filepath> file is a text file that enumerates one or more name-value pairs, one per
        line, in the format <codeph>name = value</codeph>. The <filepath>.properties</filepath> filename extension is
        customarily used, but is not required.</p>
      <ul compact="yes">
        <li>Lines beginning with the <codeph>#</codeph> character are comments.</li>
        <li>Properties specified as arguments of the <cmdname>dita</cmdname> command override those set in
            <filepath>.properties</filepath> files. <note type="restriction">For this reason,
              <parmname>args.input</parmname> and <parmname>transtype</parmname> can't be set in the
              <filepath>.properties</filepath> file.</note></li>
        <li>If you specify the same property more than once, the last instance is used.</li>
        <li>Properties not used by the selected transformation type are ignored.</li>
        <li>Properties can reference other property values defined elsewhere in the <filepath>.properties</filepath>
          file or passed by the <cmdname>dita</cmdname> command. Use the Ant
            <codeph>${<varname>property.name</varname>}</codeph> syntax.</li>
        <li>You can set properties not only for the default DITA-OT transformation types, but also for custom plugins.
        </li>
      </ul>
    </section>
    <steps>
      <step>
        <cmd>Create your <filepath>.properties</filepath> file.</cmd>
        <info>
          <note conref="../resources/conref-task.dita#ID/template-properties"/>
        </info>
        <stepxmp>For
          example:<codeblock><coderef href="../samples/properties/sequence-html5.properties"/></codeblock></stepxmp>
      </step>
      <step>
        <cmd>Reference your <filepath>.properties</filepath> file with the <cmdname>dita</cmdname> command when building
          your output.</cmd>
        <stepxmp>
          <codeblock>dita -i <varname>my.ditamap</varname> -f html5 -propertyfile <varname>my.properties</varname></codeblock>
        </stepxmp>
        <info/>
      </step>
      <step>
        <cmd>If needed, pass additional arguments to the <cmdname>dita</cmdname> command to override specific build
          parameters. </cmd>
        <stepxmp>
          <p>For example, to build output once with <xmlelement>draft</xmlelement> and
              <xmlelement>required-cleanup</xmlelement> content:</p>
          <codeblock>dita -i <varname>my.ditamap</varname> -f html5 -propertyfile <varname>my.properties</varname> -Dargs.draft=yes</codeblock>
        </stepxmp>
        <info>
          <note conref="../resources/conref-task.dita#ID/pass-input-dir"/>
        </info>
      </step>
    </steps>
  </taskbody>
</task>