Browse Source

hint to projects.xml; os-specific configuration

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276447 13f79535-47bb-0310-9956-ffa450edef68
master
Jan Materne 21 years ago
parent
commit
7e2def37d8
2 changed files with 43 additions and 1 deletions
  1. +21
    -0
      docs/faq.html
  2. +22
    -1
      xdocs/faq.xml

+ 21
- 0
docs/faq.html View File

@@ -206,6 +206,9 @@
</ul> </ul>
<h4 class="toc">How do I ...</h4> <h4 class="toc">How do I ...</h4>
<ul> <ul>
<li><a href="#implement-os-specific-configuration">
How do I realize os--specific configurations?
</a></li>
<li><a href="#adding-external-tasks"> <li><a href="#adding-external-tasks">
How do I add an external task that I've written to the How do I add an external task that I've written to the
page "External Tools and Task"? page "External Tools and Task"?
@@ -589,6 +592,20 @@
or use the zip archive instead (you can extract it using or use the zip archive instead (you can extract it using
<code>jar xf</code>).</p> <code>jar xf</code>).</p>
<p class="faq"> <p class="faq">
<a name="implement-os-specific-configuration"></a>
How do I realize os--specific configurations?
</p>
<p>The core idea is using property files which name accords to the
os-name. Then simply use the build-in property <tt>os.name</tt>.</p>
<p>For better use you should also provide a file with defaul values.
But be careful with the correct os-names. For test simply &lt;echo&gt;
the ${os.name} on all machines and you can be sure to use the right
file names.</p>
<pre class="code">
&lt;property file=&quot;${os.name}.properties&quot;/&gt;
&lt;property file=&quot;default.properties&quot;/&gt;
</pre>
<p class="faq">
<a name="adding-external-tasks"></a> <a name="adding-external-tasks"></a>
How do I add an external task that I've written to the How do I add an external task that I've written to the
page "External Tools and Task"? page "External Tools and Task"?
@@ -613,6 +630,10 @@
</ul> </ul>
<p>The preferred format for this information is a patch to <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/external.xml">this</a> <p>The preferred format for this information is a patch to <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/external.xml">this</a>
document.</p> document.</p>
<p>If you have written something bigger than a 'simple plugin' to Ant it
may be better to add the link to <a href="projects.html">projects.html</a>.
The procedure to add it is the same. The file to patch is <a href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/projects.xml">this</a>
document. The syntax of that file is the same.</p>
<p class="faq"> <p class="faq">
<a name="passing-cli-args"></a> <a name="passing-cli-args"></a>
How do I pass parameters from the command line to my How do I pass parameters from the command line to my


+ 22
- 1
xdocs/faq.xml View File

@@ -223,6 +223,23 @@
</faqsection> </faqsection>


<faqsection title="How do I ..."> <faqsection title="How do I ...">
<faq id="implement-os-specific-configuration">
<question>How do I realize os--specific configurations?</question>
<answer>
<p>The core idea is using property files which name accords to the
os-name. Then simply use the build-in property <tt>os.name</tt>.</p>
<p>For better use you should also provide a file with defaul values.
But be careful with the correct os-names. For test simply &lt;echo&gt;
the ${os.name} on all machines and you can be sure to use the right
file names.</p>
<source><![CDATA[
<property file="${os.name}.properties"/>
<property file="default.properties"/>
]]></source>
</answer>
</faq>


<faq id="adding-external-tasks"> <faq id="adding-external-tasks">
<question>How do I add an external task that I&apos;ve written to the <question>How do I add an external task that I&apos;ve written to the
page &quot;External Tools and Task&quot;?</question> page &quot;External Tools and Task&quot;?</question>
@@ -252,8 +269,12 @@
href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/external.xml">this</a> href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/external.xml">this</a>
document.</p> document.</p>


<p>If you have written something bigger than a 'simple plugin' to Ant it
may be better to add the link to <a href="projects.html">projects.html</a>.
The procedure to add it is the same. The file to patch is <a
href="http://cvs.apache.org/viewcvs.cgi/~checkout~/ant/xdocs/projects.xml">this</a>
document. The syntax of that file is the same.</p>
</answer> </answer>

</faq> </faq>


<faq id="passing-cli-args"> <faq id="passing-cli-args">


Loading…
Cancel
Save