| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="reference"/>
|
|---|
| 10 | <meta name="DC.Title" content="Adding new targets to the Ant build process"/>
|
|---|
| 11 | <meta name="abstract" content="The Ant conductor extension point is used to make new targets available to the Ant processing pipeline. This may be done as part of creating a new transform, extending pre-processing, or simply to provide Ant targets for the use of other plug-ins."/>
|
|---|
| 12 | <meta name="description" content="The Ant conductor extension point is used to make new targets available to the Ant processing pipeline. This may be done as part of creating a new transform, extending pre-processing, or simply to provide Ant targets for the use of other plug-ins."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/plugins-overview.html"/>
|
|---|
| 14 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 15 | <meta name="DC.Identifier" content="plugin-anttarget"/>
|
|---|
| 16 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 17 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 18 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 19 | <title>Adding new targets to the Ant build process</title>
|
|---|
| 20 | </head>
|
|---|
| 21 | <body id="plugin-anttarget">
|
|---|
| 22 |
|
|---|
| 23 |
|
|---|
| 24 | <h1 class="title topictitle1">Adding new targets to the Ant build process</h1>
|
|---|
| 25 |
|
|---|
| 26 |
|
|---|
| 27 | <div class="body refbody"><p class="shortdesc">The Ant conductor extension point is used to make new targets
|
|---|
| 28 | available to the Ant processing pipeline. This may be done as part
|
|---|
| 29 | of creating a new transform, extending pre-processing, or simply to
|
|---|
| 30 | provide Ant targets for the use of other plug-ins.</p>
|
|---|
| 31 |
|
|---|
| 32 | <div class="section"> <dl class="dl">
|
|---|
| 33 | <dt class="dt dlterm"><samp class="ph codeph">dita.conductor.target.relative</samp></dt>
|
|---|
| 34 |
|
|---|
| 35 | <dt class="dt dlterm"><samp class="ph codeph">dita.conductor.target</samp></dt>
|
|---|
| 36 |
|
|---|
| 37 | <dd class="dd"> <p class="p">Add Ant import to main Ant build file.</p>
|
|---|
| 38 |
|
|---|
| 39 | <div class="note remember"><span class="remembertitle">Remember:</span> The <samp class="ph codeph">dita.conductor.target</samp> extension
|
|---|
| 40 | is deprecated. Use <samp class="ph codeph">dita.conductor.target.relative</samp> instead.</div>
|
|---|
| 41 |
|
|---|
| 42 | </dd>
|
|---|
| 43 |
|
|---|
| 44 | </dl>
|
|---|
| 45 | </div>
|
|---|
| 46 |
|
|---|
| 47 | <div class="example"><h2 class="title sectiontitle">Example</h2><p class="p">To extend And processing,
|
|---|
| 48 | first place your extensions in an Ant project file within your plug-in,
|
|---|
| 49 | such as <span class="ph filepath">myAntStuff.xml</span>. Next, create
|
|---|
| 50 | a small wrapper file <span class="ph filepath">myAntStuffWrapper.xml</span> in
|
|---|
| 51 | the same directory: </p>
|
|---|
| 52 | <pre class="pre codeblock"><dummy> <import file="myAntStuff.xml"/> </dummy></pre>
|
|---|
| 53 | <p class="p">Then
|
|---|
| 54 | create the following feature: </p>
|
|---|
| 55 | <pre class="pre codeblock"><plugin id="com.example.ant">
|
|---|
| 56 | <feature extension="dita.conductor.target.relative" file="myAntStuffWrapper.xml"/>
|
|---|
| 57 | </plugin></pre>
|
|---|
| 58 | <p class="p">When the plug-in is integrated, the imports
|
|---|
| 59 | from <span class="ph filepath">myAntStuffWrapper.xml</span> will be copied into <span class="ph filepath">build.xml</span> (using
|
|---|
| 60 | the correct path). This makes targets in <span class="ph filepath">myAntStuff.xml</span> available
|
|---|
| 61 | to any other processing.</p>
|
|---|
| 62 | </div>
|
|---|
| 63 |
|
|---|
| 64 | </div>
|
|---|
| 65 |
|
|---|
| 66 | <div class="related-links">
|
|---|
| 67 | <div class="familylinks">
|
|---|
| 68 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../dev_ref/plugins-overview.html" title="The DITA Open Toolkit comes with a built in mechanism for adding in extensions through plug-ins. These plug-ins may do a wide variety of things, such as adding support for specialized DITA DTDs or Schemas, integrating processing overrides, or even providing entirely new output transforms. Plug-ins are the best way to extend the toolkit in a way that is consistent, easily sharable, and easy to preserve through toolkit upgrades.">Creating DITA-OT plug-ins</a></div>
|
|---|
| 69 | </div>
|
|---|
| 70 | </div>
|
|---|
| 71 |
|
|---|
| 72 | </body>
|
|---|
| 73 | </html>
|
|---|
