youys
/
ant
Not watched
1
0
Fork 1
Code
Releases 0 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
Browse Source

more lowercasing and other style adjustments

master
Gintas Grigelionis 7 years ago
parent
677f5275dd
commit
ecc6994f7e
29 changed files with 64 additions and 64 deletions
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. +2
    -2
      manual/Tasks/ejb.html
  2. +5
    -5
      manual/Tasks/ftp.html
  3. +1
    -1
      manual/Tasks/image.html
  4. +1
    -1
      manual/Tasks/import.html
  5. +1
    -1
      manual/Tasks/include.html
  6. +4
    -4
      manual/Tasks/javac.html
  7. +1
    -1
      manual/Tasks/jjtree.html
  8. +4
    -4
      manual/Tasks/junitreport.html
  9. +3
    -3
      manual/Tasks/macrodef.html
  10. +1
    -1
      manual/Tasks/property.html
  11. +1
    -1
      manual/Tasks/pvcstask.html
  12. +1
    -1
      manual/Tasks/replace.html
  13. +8
    -9
      manual/Tasks/rmic.html
  14. +1
    -1
      manual/Tasks/scriptdef.html
  15. +4
    -4
      manual/Tasks/serverdeploy.html
  16. +2
    -1
      manual/Tasks/sound.html
  17. +1
    -1
      manual/Tasks/sync.html
  18. +9
    -9
      manual/Tasks/xmlproperty.html
  19. +2
    -2
      manual/Tasks/zip.html
  20. +1
    -1
      manual/Types/classfileset.html
  21. +1
    -1
      manual/Types/custom-programming.html
  22. +2
    -2
      manual/Types/extensionset.html
  23. +2
    -2
      manual/Types/filelist.html
  24. +1
    -1
      manual/Types/filterchain.html
  25. +1
    -1
      manual/Types/multirootfileset.html
  26. +1
    -1
      manual/Types/namespace.html
  27. +1
    -1
      manual/Types/xmlcatalog.html
  28. +1
    -1
      manual/conceptstypeslist.html
  29. +1
    -1
      manual/dirtasks.html

+ 2
- 2
manual/Tasks/ejb.html View File

@@ -534,7 +534,7 @@ to extract all dependent classes. This means that, in addition to the classes th
the deployment descriptor, any classes that these depend on are also automatically included in the the deployment descriptor, any classes that these depend on are also automatically included in the
jar file.</p> jar file.</p>


<h3 id="naming">Naming Convention</h3>
<h3 id="naming">Naming convention</h3>


<code>Ejbjar</code> handles the processing of multiple beans, and it uses a set of naming <code>Ejbjar</code> handles the processing of multiple beans, and it uses a set of naming
conventions to determine the name of the generated EJB jars. The naming convention that is used is conventions to determine the name of the generated EJB jars. The naming convention that is used is
@@ -716,7 +716,7 @@ not, <code>ejbjar</code> will drop back to the behaviour corresponding to the va
<p>In addition to the vendor specific nested elements, the <code>ejbjar</code> task provides three <p>In addition to the vendor specific nested elements, the <code>ejbjar</code> task provides three
nested elements.</p> nested elements.</p>


<h4>Classpath</h4>
<h4>classpath</h4>


<p>The <code>&lt;classpath&gt;</code> nested element allows the classpath to be set. It is useful <p>The <code>&lt;classpath&gt;</code> nested element allows the classpath to be set. It is useful
when setting the classpath from a reference path. In all other respects the behaviour is the same as when setting the classpath from a reference path. In all other respects the behaviour is the same as


+ 5
- 5
manual/Tasks/ftp.html View File

@@ -393,7 +393,7 @@ files to be retrieved, or deleted, or listed, or whose mode you want to change.<
to <q>false</q>.</em> On remote filesets hidden files are not checked for being symbolic links. to <q>false</q>.</em> On remote filesets hidden files are not checked for being symbolic links.
Hidden files are currently assumed to not be symbolic links.</p> Hidden files are currently assumed to not be symbolic links.</p>


<h3>Sending Files</h3>
<h3>Sending files</h3>
<p>The easiest way to describe how to send files is with a couple of examples:</p> <p>The easiest way to describe how to send files is with a couple of examples:</p>
<pre> <pre>
&lt;ftp server="ftp.apache.org" &lt;ftp server="ftp.apache.org"
@@ -465,7 +465,7 @@ the <samp>/pub/incoming</samp> directory. The files are transferred in text mode
password <samp>java1</samp> and uploads all HTML files in the <samp>htdocs/manual</samp> directory password <samp>java1</samp> and uploads all HTML files in the <samp>htdocs/manual</samp> directory
to the <samp>c:\uploads</samp> directory. Progress messages are displayed as each file is to the <samp>c:\uploads</samp> directory. Progress messages are displayed as each file is
uploaded.</p> uploaded.</p>
<h3>Getting Files</h3>
<h3>Getting files</h3>
<p>Getting files from an FTP server works pretty much the same way as sending them does. The only <p>Getting files from an FTP server works pretty much the same way as sending them does. The only
difference is that the nested filesets use the <var>remotedir</var> attribute as the base directory difference is that the nested filesets use the <var>remotedir</var> attribute as the base directory
for the files on the FTP server, and the <var>dir</var> attribute as the local directory to put the for the files on the FTP server, and the <var>dir</var> attribute as the local directory to put the
@@ -514,7 +514,7 @@ names in Standard European format, as <samp>anonymous</samp>, and recursively do
all <samp>.html</samp> files from default directory for that user into all <samp>.html</samp> files from default directory for that user into
the <samp>htdocs/manual</samp> directory on the local machine.</p> the <samp>htdocs/manual</samp> directory on the local machine.</p>


<h3>Deleting Files</h3>
<h3>Deleting files</h3>
<p>As you've probably guessed by now, you use nested fileset elements to select the files to delete <p>As you've probably guessed by now, you use nested fileset elements to select the files to delete
from the remote FTP server. Again, the filesets are relative to the remote directory, not a local from the remote FTP server. Again, the filesets are relative to the remote directory, not a local
directory. In fact, the <var>dir</var> attribute of the fileset is ignored completely.</p> directory. In fact, the <var>dir</var> attribute of the fileset is ignored completely.</p>
@@ -546,7 +546,7 @@ to delete a file, a BuildException is thrown.</p>
relative to the default directory of the <samp>anonymous</samp> user. The listing is in whatever relative to the default directory of the <samp>anonymous</samp> user. The listing is in whatever
format the FTP server normally lists files.</p> format the FTP server normally lists files.</p>


<h3>Creating Directories</h3>
<h3>Creating directories</h3>
<p>Note that with the <q>mkdir</q> action, the directory to create is specified using <p>Note that with the <q>mkdir</q> action, the directory to create is specified using
the <var>remotedir</var> attribute.</p> the <var>remotedir</var> attribute.</p>
<pre> <pre>
@@ -558,7 +558,7 @@ the <var>remotedir</var> attribute.</p>
<p>This creates the directory <samp>some/remote/dir</samp> beneath the default root directory. As <p>This creates the directory <samp>some/remote/dir</samp> beneath the default root directory. As
with all other actions, the directory separator character must be correct according to the desires with all other actions, the directory separator character must be correct according to the desires
of the FTP server.</p> of the FTP server.</p>
<h3>Removing Directories</h3>
<h3>Removing directories</h3>
<p>This action uses nested fileset elements to select the directories to remove from the remote FTP <p>This action uses nested fileset elements to select the directories to remove from the remote FTP
server. The filesets are relative to the remote directory, not a local directory. server. The filesets are relative to the remote directory, not a local directory.
The <var>dir</var> attribute of the fileset is ignored completely. The directories to be removed The <var>dir</var> attribute of the fileset is ignored completely. The directories to be removed


+ 1
- 1
manual/Tasks/image.html View File

@@ -117,7 +117,7 @@ and <code>&lt;patternset&gt;</code> elements.</p>


<h4>ImageOperation</h4> <h4>ImageOperation</h4>
<p>Adds an ImageOperation to chain.</p> <p>Adds an ImageOperation to chain.</p>
<h5>Nested Elements</h5>
<h5>Nested elements</h5>
<p>ImageOperation can handle <p>ImageOperation can handle
nested <code>Rotate</code>, <code>Draw</code>, <code>Rectangle</code>, <code>Text</code> nested <code>Rotate</code>, <code>Draw</code>, <code>Rectangle</code>, <code>Text</code>
and <code>Scale</code> objects.</p> and <code>Scale</code> objects.</p>


+ 1
- 1
manual/Tasks/import.html View File

@@ -65,7 +65,7 @@
overridden target's name instead of the <var>name</var> attribute of the <code>project</code> overridden target's name instead of the <var>name</var> attribute of the <code>project</code>
tag.</p> tag.</p>


<h4>Special Properties</h4>
<h4>Special properties</h4>


<p>Imported files are treated as they are present in the main buildfile. This makes it easy to <p>Imported files are treated as they are present in the main buildfile. This makes it easy to
understand, but it makes it impossible for them to reference files and resources relative to understand, but it makes it impossible for them to reference files and resources relative to


+ 1
- 1
manual/Tasks/include.html View File

@@ -62,7 +62,7 @@
<p><code>&lt;import&gt;</code> contribute to the prefix as well, but only if their <var>as</var> <p><code>&lt;import&gt;</code> contribute to the prefix as well, but only if their <var>as</var>
attribute has been specified. attribute has been specified.


<h4>Special Properties</h4>
<h4>Special properties</h4>


<p>Included files are treated as they are present in the main buildfile. This makes it easy to <p>Included files are treated as they are present in the main buildfile. This makes it easy to
understand, but it makes it impossible for them to reference files and resources relative to understand, but it makes it impossible for them to reference files and resources relative to


+ 4
- 4
manual/Tasks/javac.html View File

@@ -668,7 +668,7 @@ compilation module set. The <code>{ ... , ... }</code> express alternates for e
compilation uses application modules located in <code>modules</code> folder.The source level compilation uses application modules located in <code>modules</code> folder.The source level
is <q>9</q> to enable modules.</p> is <q>9</q> to enable modules.</p>


<h3>Jikes Notes</h3>
<h3>Jikes notes</h3>


<p>You need Jikes 1.15 or later.</p> <p>You need Jikes 1.15 or later.</p>


@@ -710,13 +710,13 @@ are <q>false</q>.</p>
</tr> </tr>
</table> </table>


<h3>Jvc Notes</h3>
<h3>Jvc notes</h3>


<p><q>Jvc</q> will enable Microsoft extensions unless you set the <p><q>Jvc</q> will enable Microsoft extensions unless you set the
property <code>build.compiler.jvc.extensions</code> to <q>false</q> before property <code>build.compiler.jvc.extensions</code> to <q>false</q> before
invoking <code>&lt;javac&gt;</code>.</p> invoking <code>&lt;javac&gt;</code>.</p>


<h3 id="bootstrap">Bootstrap Options</h3>
<h3 id="bootstrap">Bootstrap options</h3>
<p>The Sun <code>javac</code> compiler has a <code>bootclasspath</code> command line <p>The Sun <code>javac</code> compiler has a <code>bootclasspath</code> command line
option&mdash;this corresponds to the <var>bootclasspath</var> attribute/element of option&mdash;this corresponds to the <var>bootclasspath</var> attribute/element of
the <code>&lt;javac&gt;</code> task. The Sun compiler also allows more control over the boot the <code>&lt;javac&gt;</code> task. The Sun compiler also allows more control over the boot
@@ -733,7 +733,7 @@ references to strings that can by used in an OS independent fashion
&lt;compilerarg arg="-Xbootclasspath/p:${toString:lib.path.ref}"/&gt; &lt;compilerarg arg="-Xbootclasspath/p:${toString:lib.path.ref}"/&gt;
&lt;/javac&gt;</pre> &lt;/javac&gt;</pre>


<h3>OpenJDK Notes</h3>
<h3>OpenJDK notes</h3>
<p>The <a href="http://openjdk.java.net/">openjdk</a> project has provided <p>The <a href="http://openjdk.java.net/">openjdk</a> project has provided
the <code>javac</code> <a href="http://openjdk.java.net/groups/compiler/">compiler</a> as an open the <code>javac</code> <a href="http://openjdk.java.net/groups/compiler/">compiler</a> as an open
source project. The output of this project is a <code>javac.jar</code> which contains source project. The output of this project is a <code>javac.jar</code> which contains


+ 1
- 1
manual/Tasks/jjtree.html View File

@@ -160,7 +160,7 @@ file as the JJTree grammar file with a suffix <samp>.jj</samp>.</p>
file, <samp>Parser.jj</samp>, file to <samp>build/src</samp>. The grammar option NODE_USES_PARSER is file, <samp>Parser.jj</samp>, file to <samp>build/src</samp>. The grammar option NODE_USES_PARSER is
set to <q>true</q> when invoking JJTree.</p> set to <q>true</q> when invoking JJTree.</p>


<h3>Comparison output locations between command line JJTree and different Ant <code>taskdef</code>
<h3>Comparison of output locations between command line JJTree and different Ant <code>taskdef</code>
versions</h3> versions</h3>


<table> <table>


+ 4
- 4
manual/Tasks/junitreport.html View File

@@ -119,7 +119,7 @@ using the nested <a href="../Types/fileset.html"><code>&lt;FileSet&gt;</code></a
<p>Custom versions of <samp>junit-frames.xsl</samp> or <samp>junit-noframes.xsl</samp> must adhere <p>Custom versions of <samp>junit-frames.xsl</samp> or <samp>junit-noframes.xsl</samp> must adhere
to the above conventions.</p> to the above conventions.</p>


<h3>Nested Element of the report tag</h3>
<h3>Nested element of the report tag</h3>
<h4>param</h4> <h4>param</h4>
<p><em>Since Ant 1.7</em>, the <var>report</var> tag supports nested <code>param</code> tags. These <p><em>Since Ant 1.7</em>, the <var>report</var> tag supports nested <code>param</code> tags. These
tags can pass XSL parameters to the stylesheet.</p> tags can pass XSL parameters to the stylesheet.</p>
@@ -189,15 +189,15 @@ nested <code>&lt;factory&gt;</code> can be used to specify factory settings.</p>
<p>would generate a <samp>TESTS-TestSuites.xml</samp> file in the directory <samp>reports</samp> and <p>would generate a <samp>TESTS-TestSuites.xml</samp> file in the directory <samp>reports</samp> and
generate the default framed report in the directory <samp>report/html</samp>.</p> generate the default framed report in the directory <samp>report/html</samp>.</p>


<h3>Example of report with xsl params</h3>
<h3>Example of report with XSL params</h3>
<pre> <pre>
&lt;junitreport todir="${outputdir}"&gt; &lt;junitreport todir="${outputdir}"&gt;
&lt;fileset dir="${jrdir}"&gt; &lt;fileset dir="${jrdir}"&gt;
&lt;include name="TEST-*.xml"/&gt; &lt;include name="TEST-*.xml"/&gt;
&lt;/fileset&gt; &lt;/fileset&gt;
&lt;report todir="${outputdir}/html" &lt;report todir="${outputdir}/html"
styledir="junitreport"
format="frames"&gt;
styledir="junitreport"
format="frames"&gt;
&lt;param name="key1" expression="value1"/&gt; &lt;param name="key1" expression="value1"/&gt;
&lt;param name="key2" expression="value2"/&gt; &lt;param name="key2" expression="value2"/&gt;
&lt;/report&gt; &lt;/report&gt;


+ 3
- 3
manual/Tasks/macrodef.html View File

@@ -82,7 +82,7 @@
properties.</p> properties.</p>
<p>The case of the attribute is ignored, so <code>@{myAttribute}</code> is treated the same <p>The case of the attribute is ignored, so <code>@{myAttribute}</code> is treated the same
as <code>@{MyAttribute}</code>.</p> as <code>@{MyAttribute}</code>.</p>
<h3>Parameters</h3>
<h5>Parameters</h5>
<table class="attr"> <table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>
@@ -117,7 +117,7 @@
<p>This is used to specify nested elements of the new task. The contents of the nested elements <p>This is used to specify nested elements of the new task. The contents of the nested elements
of the task instance are placed in the templated task at the tag name.</p> of the task instance are placed in the templated task at the tag name.</p>
<p>The case of the <code>element</code> name is ignored.</p> <p>The case of the <code>element</code> name is ignored.</p>
<h3>Parameters</h3>
<h5>Parameters</h5>
<table class="attr"> <table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>
@@ -155,7 +155,7 @@
the <code>text</code> element is present, then the name becomes an attribute that gets set to the <code>text</code> element is present, then the name becomes an attribute that gets set to
the nested text of the macro invocation. <em>Since Ant 1.6.1</em>.</p> the nested text of the macro invocation. <em>Since Ant 1.6.1</em>.</p>
<p>The case of the <code>text</code> name is ignored.</p> <p>The case of the <code>text</code> name is ignored.</p>
<h3>Parameters</h3>
<h5>Parameters</h5>
<table class="attr"> <table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>


+ 1
- 1
manual/Tasks/property.html View File

@@ -236,7 +236,7 @@ personal settings with a file per user.</p>
<pre>&lt;property name=&quot;foo&quot; location=&quot;my/file.txt&quot; relative=&quot;true&quot; basedir=&quot;cvs&quot;/&gt;</pre> <pre>&lt;property name=&quot;foo&quot; location=&quot;my/file.txt&quot; relative=&quot;true&quot; basedir=&quot;cvs&quot;/&gt;</pre>
<p>Stores the relative path in <code>foo</code>: <samp>cvs/my/file.txt</samp></p> <p>Stores the relative path in <code>foo</code>: <samp>cvs/my/file.txt</samp></p>


<h3>Property Files</h3>
<h3>Property files</h3>


<p>As stated, this task will load in a properties file stored in the file system, or as a resource <p>As stated, this task will load in a properties file stored in the file system, or as a resource
on a classpath. Here are some interesting facts about this feature</p> on a classpath. Here are some interesting facts about this feature</p>


+ 1
- 1
manual/Tasks/pvcstask.html View File

@@ -166,7 +166,7 @@ project within the PVCS repository to extract files from. By nesting
multiple <code>&lt;pvcsproject&gt;</code> elements under the <code>&lt;pvcs&gt;</code> task, multiple <code>&lt;pvcsproject&gt;</code> elements under the <code>&lt;pvcs&gt;</code> task,
multiple projects can be specified.</p> multiple projects can be specified.</p>


<h3>Parameters</h3>
<h5>Parameters</h5>


<table class="attr"> <table class="attr">
<tr> <tr>


+ 1
- 1
manual/Tasks/replace.html View File

@@ -138,7 +138,7 @@ based <a href="../Types/resources.html#collection">resource collections</a> as n
<p>If either the text you want to replace or the replacement text cross line boundaries, you can use <p>If either the text you want to replace or the replacement text cross line boundaries, you can use
nested elements to specify them.</p> nested elements to specify them.</p>
<p>The elements support attributes:</p> <p>The elements support attributes:</p>
<table>
<table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>
<th>Description</th> <th>Description</th>


+ 8
- 9
manual/Tasks/rmic.html View File

@@ -72,11 +72,10 @@ documentation to learn how to use it.</p>


<h4>CORBA support</h4> <h4>CORBA support</h4>


<p>Java 11 removes the CORBA and JavaEE packages and rmic no longer
supports either <code>iiop</code> nor <code>idl</code>. Starting
with Ant 1.10.3 the rmic task will fail when using either while
running Java11+ unless you fork the task and explicitly specify an
executable.</p>
<p>Java 11 removes the CORBA and JavaEE packages and <code>rmic</code> no longer supports
either <code>iiop</code> nor <code>idl</code>. Starting with Ant 1.10.3, the <code>rmic</code> task
will fail when using either while running Java 11+ unless you fork the task and explicitly specify an
executable.</p>


<h3>Parameters</h3> <h3>Parameters</h3>
<table class="attr"> <table class="attr">
@@ -163,8 +162,8 @@ documentation to learn how to use it.</p>
</tr> </tr>
<tr> <tr>
<td>iiop</td> <td>iiop</td>
<td>indicates that portable (RMI/IIOP) stubs should be
generated.<br/> See the note on CORBA support above.</td>
<td>indicates that portable (RMI/IIOP) stubs should be generated.<br/> See the note on CORBA
support above.</td>
<td>No</td> <td>No</td>
</tr> </tr>
<tr> <tr>
@@ -174,8 +173,8 @@ documentation to learn how to use it.</p>
</tr> </tr>
<tr> <tr>
<td>idl</td> <td>idl</td>
<td>indicates that IDL output files should be generated.<br/> See
the note on CORBA support above.</td>
<td>indicates that IDL output files should be generated.<br/> See the note on CORBA support
above.</td>
<td>No</td> <td>No</td>
</tr> </tr>
<tr> <tr>


+ 1
- 1
manual/Tasks/scriptdef.html View File

@@ -280,7 +280,7 @@ beanshell jar.</p>
&lt;b1 a="this is an 'a'"/&gt; &lt;b1 a="this is an 'a'"/&gt;
&lt;b2 a2="this is an 'a2' for b2"/&gt;</pre> &lt;b2 a2="this is an 'a2' for b2"/&gt;</pre>


<h3>Testing Scripts</h3>
<h3>Testing scripts</h3>


<p>The easiest way to test scripts is to use <p>The easiest way to test scripts is to use
the <a href="https://ant.apache.org/antlibs/antunit/">AntUnit</a> Ant library. This will run all the <a href="https://ant.apache.org/antlibs/antunit/">AntUnit</a> Ant library. This will run all


+ 4
- 4
manual/Tasks/serverdeploy.html View File

@@ -91,6 +91,8 @@ classpath.</p>


<h3>Vendor-specific nested elements</h3> <h3>Vendor-specific nested elements</h3>


<p>Also supported are nested vendor-specific elements.</p>

<h3>Parameters used for all tools</h3> <h3>Parameters used for all tools</h3>
<table class="attr"> <table class="attr">
<tr> <tr>
@@ -121,8 +123,6 @@ classpath.</p>
</tr> </tr>
</table> </table>


<p>Also supported are nested vendor-specific elements.</p>

<h3 id="serverdeploy_generic">Generic element</h3> <h3 id="serverdeploy_generic">Generic element</h3>
<p>This element is provided for generic Java-based deployment tools. The generic task accepts (but <p>This element is provided for generic Java-based deployment tools. The generic task accepts (but
does not require) nested <code>arg</code> and <code>jvmarg</code> elements. A JVM will be spawned does not require) nested <code>arg</code> and <code>jvmarg</code> elements. A JVM will be spawned
@@ -142,7 +142,7 @@ generic one if at all possible.</p>
</tr> </tr>
</table> </table>


<h3>Nested Elements</h3>
<h4>Nested elements</h4>
<p>The generic element supports nested <code>&lt;arg&gt;</code> and <code>&lt;jvmarg&gt;</code> <p>The generic element supports nested <code>&lt;arg&gt;</code> and <code>&lt;jvmarg&gt;</code>
elements.</p> elements.</p>


@@ -269,7 +269,7 @@ tool.</p>
</tr> </tr>
</table> </table>


<h3>Nested Elements</h3>
<h4>Nested elements</h4>
<p>The <code>jonas</code> element supports nested <code>&lt;arg&gt;</code> <p>The <code>jonas</code> element supports nested <code>&lt;arg&gt;</code>
and <code>&lt;jvmarg&gt;</code> elements.</p> and <code>&lt;jvmarg&gt;</code> elements.</p>




+ 2
- 1
manual/Tasks/sound.html View File

@@ -41,10 +41,11 @@ executed.</p>
<h3>Parameters specified as nested elements</h3> <h3>Parameters specified as nested elements</h3>
<h4>success</h4> <h4>success</h4>
<p>Specifies the sound to be played if the build succeeded.</p> <p>Specifies the sound to be played if the build succeeded.</p>

<h4>fail</h4> <h4>fail</h4>
<p>Specifies the sound to be played if the build failed.</p> <p>Specifies the sound to be played if the build failed.</p>


<h3>Nested element parameters</h3>
<h4>Nested element parameters</h4>
<p>The following attributes may be used on the <code>&lt;success&gt;</code> <p>The following attributes may be used on the <code>&lt;success&gt;</code>
and <code>&lt;fail&gt;</code> elements:</p> and <code>&lt;fail&gt;</code> elements:</p>
<table class="attr"> <table class="attr">


+ 1
- 1
manual/Tasks/sync.html View File

@@ -101,7 +101,7 @@ present in one of the source directories.</p>
support the <var>dir</var> attribute and the <var>usedefaultexcludes</var> attribute defaults support the <var>dir</var> attribute and the <var>usedefaultexcludes</var> attribute defaults
to <q>false</q>.</p> to <q>false</q>.</p>


<h5>Additional Parameters</h5>
<h5>Additional parameters</h5>
<table class="attr"> <table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>


+ 9
- 9
manual/Tasks/xmlproperty.html View File

@@ -38,7 +38,7 @@
<p>By default, this load does <em>no</em> processing of the input. In particular, unlike <p>By default, this load does <em>no</em> processing of the input. In particular, unlike
the <a href="property.html">Property task</a>, property references (i.e., <samp>${foo}</samp>) are the <a href="property.html">Property task</a>, property references (i.e., <samp>${foo}</samp>) are
not resolved.</p> not resolved.</p>
<h3 id="semanticAttributes">Semantic Attributes</h3>
<h3 id="semanticAttributes">Semantic attributes</h3>
<p>Input processing can be enabled by using the <var>semanticAttributes</var> attribute. If this <p>Input processing can be enabled by using the <var>semanticAttributes</var> attribute. If this
attribute is set to <q>true</q> (its default is <q>false</q>), the following processing occurs as attribute is set to <q>true</q> (its default is <q>false</q>), the following processing occurs as
the input XML file is loaded:/p> the input XML file is loaded:/p>
@@ -143,9 +143,9 @@ perform entity resolution.</p>


<h3 id="examples">Examples</h3> <h3 id="examples">Examples</h3>


<h4>Non-semantic Attributes</h4>
<h4>Non-semantic attributes</h4>


<p>Here is an example xml file that does not have any semantic attributes.</p>
<p>Here is an example XML file that does not have any semantic attributes.</p>


<pre> <pre>
&lt;root-tag myattr="true"&gt; &lt;root-tag myattr="true"&gt;
@@ -163,7 +163,7 @@ root-tag.inner-tag=Text
root-tag.inner-tag(someattr)=val root-tag.inner-tag(someattr)=val
root-tag.a2.a3.a4=false</pre> root-tag.a2.a3.a4=false</pre>


<h5>collapseAttributes=false</h5>
<h5><var>collapseAttributes</var>=<q>false</q></h5>
<p>This entry in a build file:</p> <p>This entry in a build file:</p>
<pre>&lt;xmlproperty file="somefile.xml" collapseAttributes="true"/&gt;</pre> <pre>&lt;xmlproperty file="somefile.xml" collapseAttributes="true"/&gt;</pre>
<p>is equivalent to the following properties:</p> <p>is equivalent to the following properties:</p>
@@ -173,7 +173,7 @@ root-tag.inner-tag=Text
root-tag.inner-tag.someatt=val root-tag.inner-tag.someatt=val
root-tag.a2.a3.a4=false</pre> root-tag.a2.a3.a4=false</pre>


<h5>keepRoot=false</h5>
<h5><var>keepRoot</var>=<q>false</q></h5>
<p>This entry in a build file:</p> <p>This entry in a build file:</p>
<pre>&lt;xmlproperty file="somefile.xml" keepRoot="false"/&gt;</pre> <pre>&lt;xmlproperty file="somefile.xml" keepRoot="false"/&gt;</pre>
<p>is equivalent to the following properties:</p> <p>is equivalent to the following properties:</p>
@@ -182,9 +182,9 @@ inner-tag=Text
inner-tag(someattr)=val inner-tag(someattr)=val
a2.a3.a4=false</pre> a2.a3.a4=false</pre>


<h4>Semantic Attributes</h4>
<h4>Semantic attributes</h4>


<p>Here is an example xml file that has semantic attributes.</p>
<p>Here is an example XML file that has semantic attributes.</p>
<pre> <pre>
&lt;root-tag&gt; &lt;root-tag&gt;
&lt;version value="0.0.1"/&gt; &lt;version value="0.0.1"/&gt;
@@ -206,7 +206,7 @@ a2.a3.a4=false</pre>
&lt;/run-time&gt; &lt;/run-time&gt;
&lt;/root-tag&gt;</pre> &lt;/root-tag&gt;</pre>


<h5>default loading (semanticAttributes=true)</h5>
<h5>default loading (<var>semanticAttributes</var>=<q>true</q>)</h5>
<p>This entry in a build file:</p> <p>This entry in a build file:</p>
<pre> <pre>
&lt;xmlproperty file="somefile.xml" keepRoot="false" &lt;xmlproperty file="somefile.xml" keepRoot="false"
@@ -229,7 +229,7 @@ a2.a3.a4=false</pre>
&lt;pathelement path="${run-time.jars}"/&gt; &lt;pathelement path="${run-time.jars}"/&gt;
&lt;/path&gt;</pre> &lt;/path&gt;</pre>


<h5>includeSemanticAttribute="true"</h5>
<h5><var>includeSemanticAttribute</var>=<q>true</q></h5>
<p>This entry in a build file:</p> <p>This entry in a build file:</p>
<pre> <pre>
&lt;xmlproperty file="somefile.xml" &lt;xmlproperty file="somefile.xml"


+ 2
- 2
manual/Tasks/zip.html View File

@@ -258,7 +258,7 @@ extract an Ant generated ZIP archive.</p>
</tr> </tr>
</table> </table>


<h3 id="encoding">Encoding of File Names</h3>
<h3 id="encoding">Encoding of file names</h3>


<p>Traditionally the ZIP archive format uses CodePage 437 as encoding for file name, which is not <p>Traditionally the ZIP archive format uses CodePage 437 as encoding for file name, which is not
sufficient for many international character sets.</p> sufficient for many international character sets.</p>
@@ -300,7 +300,7 @@ filenames that cannot be encoded using the specified encoding.</p>
name information from them, unless you set the optional name information from them, unless you set the optional
attribute <var>scanForUnicodeExtraFields</var> to <q>false</q>.</p> attribute <var>scanForUnicodeExtraFields</var> to <q>false</q>.</p>


<h4>Recommendations for Interoperability</h4>
<h4>Recommendations for interoperability</h4>


<p>The optimal setting of flags depends on the archivers you expect as consumers/producers of the <p>The optimal setting of flags depends on the archivers you expect as consumers/producers of the
ZIP archives. Below are some test results which may be superseded with later versions of each ZIP archives. Below are some test results which may be superseded with later versions of each


+ 1
- 1
manual/Types/classfileset.html View File

@@ -55,7 +55,7 @@ the <a href="fileset.html">standard fileset</a>:
</tr> </tr>
</table> </table>


<h3>Nested Elements</h3>
<h3>Nested elements</h3>


<h4>Root</h4> <h4>Root</h4>
<p> <p>


+ 1
- 1
manual/Types/custom-programming.html View File

@@ -41,7 +41,7 @@
<p> <p>
The old methods of defining custom components are still supported. The old methods of defining custom components are still supported.
</p> </p>
<h3>Definition and use</h3>
<h3>Definition and Use</h3>
<p> <p>
A custom component is a normal Java class that implements a particular A custom component is a normal Java class that implements a particular
interface or extends a particular class, or has been adapted to the interface or extends a particular class, or has been adapted to the


+ 2
- 2
manual/Types/extensionset.html View File

@@ -31,7 +31,7 @@ file <samp>guide/extensions/versioning.html</samp> or online
at <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/versioning/spec/versioning2.html#wp90779">Package at <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/versioning/spec/versioning2.html#wp90779">Package
Versioning documentation.</a></p> Versioning documentation.</a></p>


<h3>Nested Elements</h3>
<h3>Nested elements</h3>


<h4>extension</h4> <h4>extension</h4>
<p><a href="extension.html">Extension</a> object to add to set.</p> <p><a href="extension.html">Extension</a> object to add to set.</p>
@@ -40,7 +40,7 @@ Versioning documentation.</a></p>
<p><a href="fileset.html">FileSet</a>s all files contained contained within set that are jars <p><a href="fileset.html">FileSet</a>s all files contained contained within set that are jars
and implement an extension are added to extension set.</p> and implement an extension are added to extension set.</p>


<h4>LibFileSet</h4>
<h4>libfileset</h4>
<p>All files contained contained within set that are jars and implement an extension are added <p>All files contained contained within set that are jars and implement an extension are added
to extension set. However, the extension information may be modified by attributes of to extension set. However, the extension information may be modified by attributes of
libfileset.</p> libfileset.</p>


+ 2
- 2
manual/Types/filelist.html View File

@@ -50,10 +50,10 @@ support this feature or as stand-alone types.</p>
<td>Yes, unless there is a nested file element</td> <td>Yes, unless there is a nested file element</td>
</tr> </tr>
</table> </table>
<h4>Nested Element: file</h4>
<h4>Nested element: file</h4>
<p><em>Since Apache Ant 1.6.2</em></p>
<p>This represents a file name. The nested element allows filenames containing white space and <p>This represents a file name. The nested element allows filenames containing white space and
commas.</p> commas.</p>
<p><em>Since Apache Ant 1.6.2</em></p>
<table class="attr"> <table class="attr">
<tr> <tr>
<th>Attribute</th> <th>Attribute</th>


+ 1
- 1
manual/Types/filterchain.html View File

@@ -136,7 +136,7 @@ implement <code>org.apache.tools.type.Parameterizable</code>.</p>
</tr> </tr>
</table> </table>


<h4>Nested Elements</h4>
<h4>Nested elements</h4>
<p><code>&lt;filterreader&gt;</code> supports <code>&lt;classpath&gt;</code> <p><code>&lt;filterreader&gt;</code> supports <code>&lt;classpath&gt;</code>
and <code>&lt;param&gt;</code> as nested elements. Each <code>&lt;param&gt;</code> element may and <code>&lt;param&gt;</code> as nested elements. Each <code>&lt;param&gt;</code> element may
take in the following attributes&mdash;<var>name</var>, <var>type</var> and <var>value</var>.</p> take in the following attributes&mdash;<var>name</var>, <var>type</var> and <var>value</var>.</p>


+ 1
- 1
manual/Types/multirootfileset.html View File

@@ -123,7 +123,7 @@ an <code>&lt;and&gt;</code> selector container.</p>
<p>In addition basedirs for the MultiRootFileSet can be specified as nested <code>basedir</code> <p>In addition basedirs for the MultiRootFileSet can be specified as nested <code>basedir</code>
elements that have a single <var>file</var> attribute.</p> elements that have a single <var>file</var> attribute.</p>


<h4>Examples</h4>
<h3>Examples</h3>


<pre> <pre>
&lt;multirootfileset basedirs=&quot;${build.dir},${other.project.dir}&quot;&gt; &lt;multirootfileset basedirs=&quot;${build.dir},${other.project.dir}&quot;&gt;


+ 1
- 1
manual/Types/namespace.html View File

@@ -95,7 +95,7 @@
element and all its descendants. element and all its descendants.
</p> </p>


<h3>Default namespace</h3>
<h3>Default Namespace</h3>
<p> <p>
The default namespace used by Ant is <code>antlib:org.apache.tools.ant</code>. The default namespace used by Ant is <code>antlib:org.apache.tools.ant</code>.
</p> </p>


+ 1
- 1
manual/Types/xmlcatalog.html View File

@@ -89,7 +89,7 @@ and <code>URI</code> respectively. By contrast, external catalog files may use
types defined in types defined in
the <a href="https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html">OASIS the <a href="https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html">OASIS
specification</a>.</p> specification</a>.</p>
<h3 id="ResolverAlgorithm">Entity/DTD/URI Resolution Algorithm</h3>
<h3 id="ResolverAlgorithm">Entity/DTD/URI resolution algorithm</h3>
<p>When an entity, DTD, or URI is looked up by the XML processor, the XMLCatalog searches its <p>When an entity, DTD, or URI is looked up by the XML processor, the XMLCatalog searches its
list of entries to see if any match. That is, it attempts to match the <var>publicId</var> list of entries to see if any match. That is, it attempts to match the <var>publicId</var>
attribute of each entry with the PublicID or URI of the entity to be resolved. Assuming a attribute of each entry with the PublicID or URI of the entity to be resolved. Assuming a


+ 1
- 1
manual/conceptstypeslist.html View File

@@ -53,7 +53,7 @@
<li><a href="Types/filterset.html">FilterSet</a></li> <li><a href="Types/filterset.html">FilterSet</a></li>
<li><a href="Types/multirootfileset.html">MultiRootFileSet</a></li> <li><a href="Types/multirootfileset.html">MultiRootFileSet</a></li>
<li><a href="Types/patternset.html">PatternSet</a></li> <li><a href="Types/patternset.html">PatternSet</a></li>
<li><a href="using.html#path">PATH-like Structures</a></li>
<li><a href="using.html#path">Path-like Structures</a></li>
<li><a href="Types/permissions.html">Permissions</a></li> <li><a href="Types/permissions.html">Permissions</a></li>
<li><a href="Types/propertyset.html">PropertySet</a></li> <li><a href="Types/propertyset.html">PropertySet</a></li>
<li><a href="Types/redirector.html">I/O Redirectors</a></li> <li><a href="Types/redirector.html">I/O Redirectors</a></li>


+ 1
- 1
manual/dirtasks.html View File

@@ -198,7 +198,7 @@ selection criteria for the files the task should work with. See
the <a href="Types/selectors.html">Selector</a> documentation for the <a href="Types/selectors.html">Selector</a> documentation for
more information.</p> more information.</p>


<h3 id="tasklist">Standard Tasks/Filesets</h3>
<h3 id="tasklist">Standard Tasks/FileSets</h3>
<p>Many of the standard tasks in ant take one or more filesets which follow <p>Many of the standard tasks in ant take one or more filesets which follow
the rules given here. This list, a subset of those, is a list of standard ant the rules given here. This list, a subset of those, is a list of standard ant
tasks that can act as an implicit fileset:</p> tasks that can act as an implicit fileset:</p>


Write Preview
Loading…
Cancel
Save
Please read the following content carefully:

Dear OpenI User

Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.

For more agreement content, please refer to the《Openl Qizhi Community AI Collaboration Platform Usage Agreement》

Agree and continue
Disagree, exit