<td valign="top">The initial or main module to resolve. To specify
<td valign="top">The initial or main module to resolve. To specify
the module main class use the <a href="#classname">classname</a> attribute.
the module main class use the <a href="#classname">classname</a> attribute.
Fork must be set to true if this option is selected.<em>since Ant 1.9.7</em></td>
Fork must be set to true if this option is selected.<em>since Ant 1.9.7</em></td>
<td align="center" valign="top">Either <tt>jar</tt>, <tt>classname</tt> or <tt>module</tt></td>
<td align="center" valign="top">Either <tt>jar</tt>, <tt>classname</tt> or <tt>module</tt></td>
</tr>
</tr>
<tr>
<tr>
<td valign="top">modulepath</td>
<td valign="top">modulepath</td>
<td valign="top">Specify where to find application modules. A list of directories of modules, module files or exploded modules.<em>since Ant 1.9.7</em></td>
<td valign="top">Specify where to find application modules. A list of directories of modules, module files or exploded modules.<em>since Ant 1.9.7</em></td>
<td align="center" valign="top">No</td>
<td align="center" valign="top">No</td>
</tr>
</tr>
<tr>
<tr>
@@ -283,7 +283,7 @@ see <a href="../Types/permissions.html">permissions</a></p>
<p>When the permission RuntimePermission exitVM has not been granted (or has
<p>When the permission RuntimePermission exitVM has not been granted (or has
been revoked) the System.exit() call will be intercepted
been revoked) the System.exit() call will be intercepted
and treated like indicated in <i>failonerror</i>.</p>
and treated like indicated in <i>failonerror</i>.</p>
<p>Note:<br>
<p><strong>Note</strong>:<br>
If you do not specify permissions,
If you do not specify permissions,
a set of default permissions will be added to your Java invocation to make
a set of default permissions will be added to your Java invocation to make
sure that the Ant run will continue or terminated as indicated by
sure that the Ant run will continue or terminated as indicated by
@@ -303,7 +303,7 @@ subelement.</p>
<p>Assertion statements are currently ignored in non-forked mode.</p>
<p>Assertion statements are currently ignored in non-forked mode.</p>
@@ -35,18 +35,18 @@ and management costs over time. This task, however, has no notion of
"changed" files, unlike the <a href="javac.html">javac</a> task. This means
"changed" files, unlike the <a href="javac.html">javac</a> task. This means
all packages will be processed each time this task is run. In general, however,
all packages will be processed each time this task is run. In general, however,
this task is used much less frequently.</p>
this task is used much less frequently.</p>
<p>NOTE: since javadoc calls System.exit(), javadoc cannot be run inside the
<p><strong>Note</strong>: since javadoc calls System.exit(), javadoc cannot be run inside the
same VM as Apache Ant without breaking functionality. For this reason, this task
same VM as Apache Ant without breaking functionality. For this reason, this task
always forks the VM. This overhead is not significant since javadoc is normally a heavy
always forks the VM. This overhead is not significant since javadoc is normally a heavy
application and will be called infrequently.</p>
application and will be called infrequently.</p>
<p>NOTE: the packagelist attribute allows you to specify the list of packages to
<p><strong>Note</strong>: the packagelist attribute allows you to specify the list of packages to
document outside of the Ant file. It's a much better practice to include everything
document outside of the Ant file. It's a much better practice to include everything
inside the <code>build.xml</code> file. This option was added in order to make it easier to
inside the <code>build.xml</code> file. This option was added in order to make it easier to
migrate from regular makefiles, where you would use this option of javadoc.
migrate from regular makefiles, where you would use this option of javadoc.
The packages listed in packagelist are not checked, so the task performs even
The packages listed in packagelist are not checked, so the task performs even
if some packages are missing or broken. Use this option if you wish to convert from
if some packages are missing or broken. Use this option if you wish to convert from
an existing makefile. Once things are running you should then switch to the regular
an existing makefile. Once things are running you should then switch to the regular
notation.</p>
notation.</p>
<p><i><b>DEPRECATION:</b> the javadoc2 task simply points to the javadoc task and it's
<p><i><b>DEPRECATION:</b> the javadoc2 task simply points to the javadoc task and it's
there for back compatibility reasons. Since this task will be removed in future
there for back compatibility reasons. Since this task will be removed in future
@@ -59,14 +59,14 @@ any VM of at least version 1.2 is acceptable. JDKs <1.4 are no longer support
If you specify the <code>executable</code> attribute it is up to you
If you specify the <code>executable</code> attribute it is up to you
to ensure that this command supports the attributes you wish to use.</p>
to ensure that this command supports the attributes you wish to use.</p>
<p><b>Note:</b><br>When generating the JavaDocs for classes which contains annotations
<p><strong>Note</strong>:<br>When generating the JavaDocs for classes which contains annotations
you maybe get a <tt>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</tt>.
you maybe get a <tt>java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl</tt>.
This is due <a href="https://bugs.openjdk.java.net/browse/JDK-6442982" target="_blank">bug-6442982</a>. The cause is that JavaDoc cannot find the implementations of used annotations.
This is due <a href="https://bugs.openjdk.java.net/browse/JDK-6442982" target="_blank">bug-6442982</a>. The cause is that JavaDoc cannot find the implementations of used annotations.
The workaround is providing the jars with these implementations (like JAXBs <tt>@XmlType</tt>, ...)
The workaround is providing the jars with these implementations (like JAXBs <tt>@XmlType</tt>, ...)
to <javadoc> using <tt>classpath</tt>, <tt>classpathref</tt> attributes or nested
to <javadoc> using <tt>classpath</tt>, <tt>classpathref</tt> attributes or nested
<classpath> element.</p>
<classpath> element.</p>
<p><b>Note:</b> many problems with running javadoc stem from command
<p><strong>Note</strong>: many problems with running javadoc stem from command
lines that have become too long - even though the error message
lines that have become too long - even though the error message
doesn't give the slightest hint this may be the problem. If you
doesn't give the slightest hint this may be the problem. If you
encounter problems with the task, try to set
encounter problems with the task, try to set
@@ -208,9 +208,9 @@ to <javadoc> using <tt>classpath</tt>, <tt>classpathref</tt> attributes or
<td valign="top">Old</td>
<td valign="top">Old</td>
<td valign="top">Generate output using JDK 1.1 emulating
<td valign="top">Generate output using JDK 1.1 emulating
doclet.<br>
doclet.<br>
<b>Note:</b> as of Ant 1.8.0 this attribute doesn't have any
effect since the javadoc of Java 1.4 (required by Ant 1.8.0)
doesn't support the -1.1 switch anymore.</td>
<strong>Note</strong>: <em>Since Ant 1.8.0</em> this attribute has no
effect since javadoc of Java 1.4 and later
does not support the -1.1 switch anymore.</td>
<td align="center" valign="top">1.2</td>
<td align="center" valign="top">1.2</td>
<td align="center" valign="top">No</td>
<td align="center" valign="top">No</td>
</tr>
</tr>
@@ -791,12 +791,12 @@ not set the description attribute for those tags.</p>
<td valign="top">Name of the property whose value is to serve as the replacement value.</td>
<td valign="top">Name of the property whose value is to serve as the replacement value.</td>
</tr>
</tr>
</table>
</table>
<p>Since Ant 1.8.0 token and value can be specified as nested elements
<p><em>Since Ant 1.8.0</em> token and value can be specified as nested elements
just like in the task itself.</p>
just like in the task itself.</p>
<p>If neither <i>value</i> nor <i>property</i> is used, the value provided using the <code><replace></code> attribute <i>value</i> and/or the <code><replacevalue></code> element is used. If no value was specified using either of these options, the token is replaced with an empty string.
<p>If neither <i>value</i> nor <i>property</i> is used, the value provided using the <code><replace></code> attribute <i>value</i> and/or the <code><replacevalue></code> element is used. If no value was specified using either of these options, the token is replaced with an empty string.
<p>In file <code>configure.sh</code>, replace all instances of "@token1@" with "defaultvalue", all instances of "@token2@" with "value2", and all instances of "@token3@" with the value of the property "property.key", as it appears in property file <code>src/name.properties</code>.</p>
<p>In file <code>configure.sh</code>, replace all instances of "@token1@" with "defaultvalue", all instances of "@token2@" with "value2", and all instances of "@token3@" with the value of the property "property.key", as it appears in property file <code>src/name.properties</code>.</p>
<p><b>Note:</b> It is possible to use either the <i>token</i>/<code><replacetoken></code> and <i>value</i>/<code><replacevalue></code> attributes/elements, the nested replacefilter elements, or both in the same operation.
</p>
<p><strong>Note</strong>: It is possible to use either the <i>token</i>/<code><replacetoken></code> and <i>value</i>/<code><replacevalue></code> attributes/elements, the nested replacefilter elements, or both in the same operation.</p>
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.
Gintas Grigelionis