Last change
on this file since 99527 was 98584, checked in by vboxsync, 2 years ago |
Docs: bugref:10302. Setting svn properties of DITA-OT library.
|
-
Property svn:eol-style
set to
native
-
Property svn:keywords
set to
Author Date Id Revision
|
File size:
1.1 KB
|
Line | |
---|
1 | <?xml version="1.0" encoding="UTF-8"?>
|
---|
2 | <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
---|
3 | <concept id="command-line-tool">
|
---|
4 | <title>Command-line tool</title>
|
---|
5 | <shortdesc>The DITA Open Toolkit (DITA-OT) provides a command-line tool for users with little
|
---|
6 | knowledge of Ant. The command-line tool supports a subset of the parameters that are available to
|
---|
7 | the Ant builds.</shortdesc>
|
---|
8 | <prolog>
|
---|
9 | <metadata>
|
---|
10 | <keywords>
|
---|
11 | <indexterm>command-line tool<indexterm>overview</indexterm></indexterm>
|
---|
12 | </keywords>
|
---|
13 | </metadata>
|
---|
14 | </prolog>
|
---|
15 | <conbody>
|
---|
16 | <p>The command-line tool is a wrapper around the Ant interface; it takes the simplified parameters
|
---|
17 | as input, converts them to Ant parameters, and then runs an Ant build. The Ant parameters that
|
---|
18 | are passed to the DITA-OT are saved to the <filepath>property.temp</filepath> file that is
|
---|
19 | written to the output directory.</p>
|
---|
20 | <p>For individual builds, the additional Java overhead is minimal, but for repeated or
|
---|
21 | server-based builds, the extra memory usage might become an issue. Applications that embed the
|
---|
22 | toolkit should invoke Ant directly.</p>
|
---|
23 | </conbody>
|
---|
24 | </concept>
|
---|
Note:
See
TracBrowser
for help on using the repository browser.