Modified: maven/website/components/plugins-archives/maven-clean-plugin-LATEST/clean-mojo.html ============================================================================== --- maven/website/components/plugins-archives/maven-clean-plugin-LATEST/clean-mojo.html (original) +++ maven/website/components/plugins-archives/maven-clean-plugin-LATEST/clean-mojo.html Sun Jun 16 10:28:13 2024 @@ -1,6 +1,6 @@ <!DOCTYPE html> <!-- - | Generated by Apache Maven Doxia Site Renderer 1.11.1 from target/generated-site/xdoc/clean-mojo.xml at 2023-10-23 + | Generated by Apache Maven Doxia Site Renderer 1.11.1 from org.apache.maven.plugins:maven-plugin-report-plugin:3.12.0:report at 2024-06-16 | Rendered using Apache Maven Fluido Skin 1.9 --> <html xmlns="http://www.w3.org/1999/xhtml"; lang="en"> @@ -30,8 +30,8 @@ <li class=""><a href="../index.html" title="Plugins">Plugins</a><span class="divider">/</span></li> <li class=""><a href="index.html" title="Apache Maven Clean Plugin">Apache Maven Clean Plugin</a><span class="divider">/</span></li> <li class="active ">clean:clean</li> - <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2023-10-23</li> - <li id="projectVersion" class="pull-right">Version: 3.3.2</li> + <li id="publishDate" class="pull-right"><span class="divider">|</span> Last Published: 2024-06-16</li> + <li id="projectVersion" class="pull-right">Version: 3.4.0</li> </ul> </div> </header> @@ -94,117 +94,58 @@ </div> </header> <main id="bodyColumn" class="span10" > - - - <section> -<h2><a name="clean:clean"></a>clean:clean</h2> - -<p><b>Full name</b>:</p> - -<p>org.apache.maven.plugins:maven-clean-plugin:3.3.2:clean</p> - -<p><b>Description</b>:</p> - -<div>Goal which cleans the build. - +<section> +<h2><a name="clean:clean"></a>clean:clean</h2><a name="clean:clean"></a> +<p><strong>Full name</strong>:</p> +<p>org.apache.maven.plugins:maven-clean-plugin:3.4.0:clean</p> +<p><strong>Description</strong>:</p> +<p>Goal which cleans the build. <p>This attempts to clean a project's working directory of the files that were generated at build-time. By default, it discovers and deletes the directories configured in <code>project.build.directory</code>, <code>project.build.outputDirectory</code>, <code>project.build.testOutputDirectory</code>, and <code>project.reporting.outputDirectory</code>.</p> - -<p>Files outside the default may also be included in the deletion by configuring the <code>filesets</code> tag.</p><br /><b>See also:</b> <a href="apidocs/org/apache/maven/plugins/clean/Fileset.html">Fileset</a></div> - -<p><b>Attributes</b>:</p> - +<p>Files outside the default may also be included in the deletion by configuring the <code>filesets</code> tag.</p><br /><strong>See also:</strong> <a href="apidocs/org/apache/maven/plugins/clean/Fileset.html">Fileset</a></p> +<p><strong>Attributes</strong>:</p> <ul> - <li>Requires a Maven project to be executed.</li> - <li>The goal is thread-safe and supports parallel builds.</li> - -<li>Since version: <code>2.0</code>.</li> - </ul> - <section> -<h3><a name="Optional_Parameters"></a>Optional Parameters</h3> - +<li>Since version: <code>2.0</code>.</li></ul><section> +<h3><a name="Optional_Parameters"></a>Optional Parameters</h3><a name="Optional_Parameters"></a> <table border="0" class="table table-striped"> - <tr class="a"> - <th>Name</th> - <th>Type</th> - <th>Since</th> - -<th>Description</th> - </tr> - +<th>Description</th></tr> <tr class="b"> - -<td align="left"><code><a href="#excludeDefaultDirectories"><excludeDefaultDirectories></a></code></td> - +<td align="left"><a href="#excludeDefaultDirectories"><code><excludeDefaultDirectories></code></a></td> <td><code>boolean</code></td> - <td><code>2.3</code></td> - <td>Disables the deletion of the default output directories configured for a project. If set to <code>true</code>, only the files/directories selected via the parameter <a href="#filesets"><code>filesets</code></a> will be deleted. <br /> - Starting with <b>3.0.0</b> the property has been renamed from <code>clean.excludeDefaultDirectories</code> to <code>maven.clean.excludeDefaultDirectories</code>.<br /><b>Default value is</b>: <code>false</code>.<br /><b>User property is</b>: <code>maven.clean.excludeDefaultDirectories</code>.<br /></td> - </tr> - + Starting with <b>3.0.0</b> the property has been renamed from <code>clean.excludeDefaultDirectories</code> to <code>maven.clean.excludeDefaultDirectories</code>.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>maven.clean.excludeDefaultDirectories</code></td></tr> <tr class="a"> - -<td align="left"><code><a href="#failOnError"><failOnError></a></code></td> - +<td align="left"><a href="#failOnError"><code><failOnError></code></a></td> <td><code>boolean</code></td> - <td><code>2.2</code></td> - -<td>Indicates whether the build will continue even if there are clean errors.<br /><b>Default value is</b>: <code>true</code>.<br /><b>User property is</b>: <code>maven.clean.failOnError</code>.<br /></td> - </tr> - +<td>Indicates whether the build will continue even if there are clean errors.<br /><strong>Default</strong>: <code>true</code><br /><strong>User Property</strong>: <code>maven.clean.failOnError</code></td></tr> <tr class="b"> - -<td align="left"><code><a href="#fast"><fast></a></code></td> - +<td align="left"><a href="#fast"><code><fast></code></a></td> <td><code>boolean</code></td> - <td><code>3.2</code></td> - -<td>Enables fast clean if possible. If set to <code>true</code>, when the plugin is executed, a directory to be deleted will be atomically moved inside the <code>maven.clean.fastDir</code> directory and a thread will be launched to delete the needed files in the background. When the build is completed, maven will wait until all the files have been deleted. If any problem occurs during the atomic move of the directories, the plugin will default to the traditional deletion mechanism.<br /><b>Default value is</b>: <code>false</code>.<br /><b>User property is</b>: <code>maven.clean.fast</code>.<br /></td> - </tr> - +<td>Enables fast clean if possible. If set to <code>true</code>, when the plugin is executed, a directory to be deleted will be atomically moved inside the <code>maven.clean.fastDir</code> directory and a thread will be launched to delete the needed files in the background. When the build is completed, maven will wait until all the files have been deleted. If any problem occurs during the atomic move of the directories, the plugin will default to the traditional deletion mechanism.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>maven.clean.fast</code></td></tr> <tr class="a"> - -<td align="left"><code><a href="#fastDir"><fastDir></a></code></td> - +<td align="left"><a href="#fastDir"><code><fastDir></code></a></td> <td><code>File</code></td> - <td><code>3.2</code></td> - -<td>When fast clean is specified, the <code>fastDir</code> property will be used as the location where directories to be deleted will be moved prior to background deletion. If not specified, the <code>${maven.multiModuleProjectDirectory}/target/.clean</code> directory will be used. If the <code>${build.directory}</code> has been modified, you'll have to adjust this property explicitly. In order for fast clean to work correctly, this directory and the various directories that will be deleted should usually reside on the same volume. The exact conditions are system dependant though, but if an atomic move is not supported, the standard deletion mechanism will be used.<br /><b>See also:</b> <a href="#fast">fast</a><br /><b>User property is</b>: <code>maven.clean.fastDir</code>.<br /></td> - </tr> - +<td>When fast clean is specified, the <code>fastDir</code> property will be used as the location where directories to be deleted will be moved prior to background deletion. If not specified, the <code>${maven.multiModuleProjectDirectory}/target/.clean</code> directory will be used. If the <code>${build.directory}</code> has been modified, you'll have to adjust this property explicitly. In order for fast clean to work correctly, this directory and the various directories that will be deleted should usually reside on the same volume. The exact conditions are system dependant though, but if an atomic move is not supported, the standard deletion mechanism will be used.<br /><strong>See also:</strong> <a href="#fast">fast</a><br /><strong>User Property</strong>: <code>maven.clean.fastDir</code></td></tr> <tr class="b"> - -<td align="left"><code><a href="#fastMode"><fastMode></a></code></td> - +<td align="left"><a href="#fastMode"><code><fastMode></code></a></td> <td><code>String</code></td> - <td><code>3.2</code></td> - -<td>Mode to use when using fast clean. Values are: <code>background</code> to start deletion immediately and waiting for all files to be deleted when the session ends, <code>at-end</code> to indicate that the actual deletion should be performed synchronously when the session ends, or <code>defer</code> to specify that the actual file deletion should be started in the background when the session ends (this should only be used when maven is embedded in a long running process).<br /><b>See also:</b> <a href="#fast">fast</a><br /><b>Default value is</b>: <code>background</code>.<br /><b>User property is</b>: <code>maven.clean.fastMode</code>.<br /></td> - </tr> - +<td>Mode to use when using fast clean. Values are: <code>background</code> to start deletion immediately and waiting for all files to be deleted when the session ends, <code>at-end</code> to indicate that the actual deletion should be performed synchronously when the session ends, or <code>defer</code> to specify that the actual file deletion should be started in the background when the session ends (this should only be used when maven is embedded in a long running process).<br /><strong>See also:</strong> <a href="#fast">fast</a><br /><strong>Default</strong>: <code>background</code><br /><strong>User Property</strong>: <code>maven.clean.fastMode</code></td></tr> <tr class="a"> - -<td align="left"><code><a href="#filesets"><filesets></a></code></td> - -<td><code><a href="apidocs/org/apache/maven/plugins/clean/Fileset.html">Fileset[]</a></code></td> - +<td align="left"><a href="#filesets"><code><filesets></code></a></td> +<td><a href="apidocs/org/apache/maven/plugins/clean/Fileset.html"><code>Fileset[]</code></a></td> <td><code>2.1</code></td> - <td>The list of file sets to delete, in addition to the default directories. For example: - -<div> <pre><filesets> <fileset> <directory>src/main/generated</directory> @@ -218,148 +159,77 @@ </excludes> </fileset> </filesets> -</pre></div><br /></td> - </tr> - +</pre></td></tr> <tr class="b"> - -<td align="left"><code><a href="#followSymLinks"><followSymLinks></a></code></td> - +<td align="left"><a href="#followSymLinks"><code><followSymLinks></code></a></td> <td><code>boolean</code></td> - <td><code>2.1</code></td> - <td>Sets whether the plugin should follow symbolic links while deleting files from the default output directories of the project. Not following symlinks requires more IO operations and heap memory, regardless whether symlinks are actually present. So projects with a huge output directory that knowingly does not contain symlinks can improve performance by setting this parameter to <code>true</code>. <br /> - Starting with <code>3.0.0</code> the property has been renamed from <code>clean.followSymLinks</code> to <code>maven.clean.followSymLinks</code>.<br /><b>Default value is</b>: <code>false</code>.<br /><b>User property is</b>: <code>maven.clean.followSymLinks</code>.<br /></td> - </tr> - + Starting with <code>3.0.0</code> the property has been renamed from <code>clean.followSymLinks</code> to <code>maven.clean.followSymLinks</code>.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>maven.clean.followSymLinks</code></td></tr> <tr class="a"> - -<td align="left"><code><a href="#retryOnError"><retryOnError></a></code></td> - +<td align="left"><a href="#retryOnError"><code><retryOnError></code></a></td> <td><code>boolean</code></td> - <td><code>2.4.2</code></td> - -<td>Indicates whether the plugin should undertake additional attempts (after a short delay) to delete a file if the first attempt failed. This is meant to help deleting files that are temporarily locked by third-party tools like virus scanners or search indexing.<br /><b>Default value is</b>: <code>true</code>.<br /><b>User property is</b>: <code>maven.clean.retryOnError</code>.<br /></td> - </tr> - +<td>Indicates whether the plugin should undertake additional attempts (after a short delay) to delete a file if the first attempt failed. This is meant to help deleting files that are temporarily locked by third-party tools like virus scanners or search indexing.<br /><strong>Default</strong>: <code>true</code><br /><strong>User Property</strong>: <code>maven.clean.retryOnError</code></td></tr> <tr class="b"> - -<td align="left"><code><a href="#skip"><skip></a></code></td> - +<td align="left"><a href="#skip"><code><skip></code></a></td> <td><code>boolean</code></td> - <td><code>2.2</code></td> - <td>Disables the plugin execution. <br /> - Starting with <code>3.0.0</code> the property has been renamed from <code>clean.skip</code> to <code>maven.clean.skip</code>.<br /><b>Default value is</b>: <code>false</code>.<br /><b>User property is</b>: <code>maven.clean.skip</code>.<br /></td> - </tr> - + Starting with <code>3.0.0</code> the property has been renamed from <code>clean.skip</code> to <code>maven.clean.skip</code>.<br /><strong>Default</strong>: <code>false</code><br /><strong>User Property</strong>: <code>maven.clean.skip</code></td></tr> <tr class="a"> - -<td align="left"><code><a href="#verbose"><verbose></a></code></td> - +<td align="left"><a href="#verbose"><code><verbose></code></a></td> <td><code>Boolean</code></td> - <td><code>2.1</code></td> - <td>Sets whether the plugin runs in verbose mode. As of plugin version 2.3, the default value is derived from Maven's global debug flag (compare command line switch <code>-X</code>). <br /> - Starting with <b>3.0.0</b> the property has been renamed from <code>clean.verbose</code> to <code>maven.clean.verbose</code>.<br /><b>User property is</b>: <code>maven.clean.verbose</code>.<br /></td> - </tr> - </table> - </section> - <section> -<h3><a name="Parameter_Details"></a>Parameter Details</h3> - <section> -<h4><a name="a.3CexcludeDefaultDirectories.3E"></a><b><a name="excludeDefaultDirectories"><excludeDefaultDirectories></a></b></h4> - + Starting with <b>3.0.0</b> the property has been renamed from <code>clean.verbose</code> to <code>maven.clean.verbose</code>.<br /><strong>User Property</strong>: <code>maven.clean.verbose</code></td></tr></table></section><section> +<h3><a name="Parameter_Details"></a>Parameter Details</h3><a name="Parameter_Details"></a><a name="excludeDefaultDirectories"><section> +<h4><a name="a.3CexcludeDefaultDirectories.3E"></a><excludeDefaultDirectories></h4><a name="a.3CexcludeDefaultDirectories.3E"></a></a> <div>Disables the deletion of the default output directories configured for a project. If set to <code>true</code>, only the files/directories selected via the parameter <a href="#filesets"><code>filesets</code></a> will be deleted. <br /> Starting with <b>3.0.0</b> the property has been renamed from <code>clean.excludeDefaultDirectories</code> to <code>maven.clean.excludeDefaultDirectories</code>.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>2.3</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.excludeDefaultDirectories</code></li> - -<li><b>Default</b>: <code>false</code></li> - </ul><hr /></section><section> -<h4><a name="a.3CfailOnError.3E"></a><b><a name="failOnError"><failOnError></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>2.3</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.excludeDefaultDirectories</code></li> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a name="failOnError"><section> +<h4><a name="a.3CfailOnError.3E"></a><failOnError></h4><a name="a.3CfailOnError.3E"></a></a> <div>Indicates whether the build will continue even if there are clean errors.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>2.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.failOnError</code></li> - -<li><b>Default</b>: <code>true</code></li> - </ul><hr /></section><section> -<h4><a name="a.3Cfast.3E"></a><b><a name="fast"><fast></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>2.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.failOnError</code></li> +<li><strong>Default</strong>: <code>true</code></li></ul><hr /></section><a name="fast"><section> +<h4><a name="a.3Cfast.3E"></a><fast></h4><a name="a.3Cfast.3E"></a></a> <div>Enables fast clean if possible. If set to <code>true</code>, when the plugin is executed, a directory to be deleted will be atomically moved inside the <code>maven.clean.fastDir</code> directory and a thread will be launched to delete the needed files in the background. When the build is completed, maven will wait until all the files have been deleted. If any problem occurs during the atomic move of the directories, the plugin will default to the traditional deletion mechanism.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>3.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.fast</code></li> - -<li><b>Default</b>: <code>false</code></li> - </ul><hr /></section><section> -<h4><a name="a.3CfastDir.3E"></a><b><a name="fastDir"><fastDir></a></b></h4> - -<div>When fast clean is specified, the <code>fastDir</code> property will be used as the location where directories to be deleted will be moved prior to background deletion. If not specified, the <code>${maven.multiModuleProjectDirectory}/target/.clean</code> directory will be used. If the <code>${build.directory}</code> has been modified, you'll have to adjust this property explicitly. In order for fast clean to work correctly, this directory and the various directories that will be deleted should usually reside on the same volume. The exact conditions are system dependant though, but if an atomic move is not supported, the standard deletion mechanism will be used.<br /><b>See also:</b> <a href="#fast">fast</a></div> - -<ul> - -<li><b>Type</b>: <code>java.io.File</code></li> - -<li><b>Since</b>: <code>3.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.fastDir</code></li> - </ul><hr /></section><section> -<h4><a name="a.3CfastMode.3E"></a><b><a name="fastMode"><fastMode></a></b></h4> - -<div>Mode to use when using fast clean. Values are: <code>background</code> to start deletion immediately and waiting for all files to be deleted when the session ends, <code>at-end</code> to indicate that the actual deletion should be performed synchronously when the session ends, or <code>defer</code> to specify that the actual file deletion should be started in the background when the session ends (this should only be used when maven is embedded in a long running process).<br /><b>See also:</b> <a href="#fast">fast</a></div> - -<ul> - -<li><b>Type</b>: <code>java.lang.String</code></li> - -<li><b>Since</b>: <code>3.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.fastMode</code></li> - -<li><b>Default</b>: <code>background</code></li> - </ul><hr /></section><section> -<h4><a name="a.3Cfilesets.3E"></a><b><a name="filesets"><filesets></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>3.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.fast</code></li> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a name="fastDir"><section> +<h4><a name="a.3CfastDir.3E"></a><fastDir></h4><a name="a.3CfastDir.3E"></a></a> +<div>When fast clean is specified, the <code>fastDir</code> property will be used as the location where directories to be deleted will be moved prior to background deletion. If not specified, the <code>${maven.multiModuleProjectDirectory}/target/.clean</code> directory will be used. If the <code>${build.directory}</code> has been modified, you'll have to adjust this property explicitly. In order for fast clean to work correctly, this directory and the various directories that will be deleted should usually reside on the same volume. The exact conditions are system dependant though, but if an atomic move is not supported, the standard deletion mechanism will be used.<br /><strong>See also:</strong> <a href="#fast">fast</a></div> +<ul> +<li><strong>Type</strong>: <code>java.io.File</code></li> +<li><strong>Since</strong>: <code>3.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.fastDir</code></li></ul><hr /></section><a name="fastMode"><section> +<h4><a name="a.3CfastMode.3E"></a><fastMode></h4><a name="a.3CfastMode.3E"></a></a> +<div>Mode to use when using fast clean. Values are: <code>background</code> to start deletion immediately and waiting for all files to be deleted when the session ends, <code>at-end</code> to indicate that the actual deletion should be performed synchronously when the session ends, or <code>defer</code> to specify that the actual file deletion should be started in the background when the session ends (this should only be used when maven is embedded in a long running process).<br /><strong>See also:</strong> <a href="#fast">fast</a></div> +<ul> +<li><strong>Type</strong>: <code>java.lang.String</code></li> +<li><strong>Since</strong>: <code>3.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.fastMode</code></li> +<li><strong>Default</strong>: <code>background</code></li></ul><hr /></section><a name="filesets"><section> +<h4><a name="a.3Cfilesets.3E"></a><filesets></h4><a name="a.3Cfilesets.3E"></a></a> <div>The list of file sets to delete, in addition to the default directories. For example: - -<div> <pre><filesets> <fileset> <directory>src/main/generated</directory> @@ -373,88 +243,48 @@ </excludes> </fileset> </filesets> -</pre></div></div> - +</pre></div> <ul> - -<li><b>Type</b>: <code><a href="apidocs/org/apache/maven/plugins/clean/Fileset.html">org.apache.maven.plugins.clean.Fileset[]</a></code></li> - -<li><b>Since</b>: <code>2.1</code></li> - -<li><b>Required</b>: <code>No</code></li> - </ul><hr /></section><section> -<h4><a name="a.3CfollowSymLinks.3E"></a><b><a name="followSymLinks"><followSymLinks></a></b></h4> - +<li><strong>Type</strong>: <a href="apidocs/org/apache/maven/plugins/clean/Fileset.html"><code>org.apache.maven.plugins.clean.Fileset[]</code></a></li> +<li><strong>Since</strong>: <code>2.1</code></li> +<li><strong>Required</strong>: <code>No</code></li></ul><hr /></section><a name="followSymLinks"><section> +<h4><a name="a.3CfollowSymLinks.3E"></a><followSymLinks></h4><a name="a.3CfollowSymLinks.3E"></a></a> <div>Sets whether the plugin should follow symbolic links while deleting files from the default output directories of the project. Not following symlinks requires more IO operations and heap memory, regardless whether symlinks are actually present. So projects with a huge output directory that knowingly does not contain symlinks can improve performance by setting this parameter to <code>true</code>. <br /> Starting with <code>3.0.0</code> the property has been renamed from <code>clean.followSymLinks</code> to <code>maven.clean.followSymLinks</code>.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>2.1</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.followSymLinks</code></li> - -<li><b>Default</b>: <code>false</code></li> - </ul><hr /></section><section> -<h4><a name="a.3CretryOnError.3E"></a><b><a name="retryOnError"><retryOnError></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>2.1</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.followSymLinks</code></li> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a name="retryOnError"><section> +<h4><a name="a.3CretryOnError.3E"></a><retryOnError></h4><a name="a.3CretryOnError.3E"></a></a> <div>Indicates whether the plugin should undertake additional attempts (after a short delay) to delete a file if the first attempt failed. This is meant to help deleting files that are temporarily locked by third-party tools like virus scanners or search indexing.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>2.4.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.retryOnError</code></li> - -<li><b>Default</b>: <code>true</code></li> - </ul><hr /></section><section> -<h4><a name="a.3Cskip.3E"></a><b><a name="skip"><skip></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>2.4.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.retryOnError</code></li> +<li><strong>Default</strong>: <code>true</code></li></ul><hr /></section><a name="skip"><section> +<h4><a name="a.3Cskip.3E"></a><skip></h4><a name="a.3Cskip.3E"></a></a> <div>Disables the plugin execution. <br /> Starting with <code>3.0.0</code> the property has been renamed from <code>clean.skip</code> to <code>maven.clean.skip</code>.</div> - <ul> - -<li><b>Type</b>: <code>boolean</code></li> - -<li><b>Since</b>: <code>2.2</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.skip</code></li> - -<li><b>Default</b>: <code>false</code></li> - </ul><hr /></section><section> -<h4><a name="a.3Cverbose.3E"></a><b><a name="verbose"><verbose></a></b></h4> - +<li><strong>Type</strong>: <code>boolean</code></li> +<li><strong>Since</strong>: <code>2.2</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.skip</code></li> +<li><strong>Default</strong>: <code>false</code></li></ul><hr /></section><a name="verbose"><section> +<h4><a name="a.3Cverbose.3E"></a><verbose></h4><a name="a.3Cverbose.3E"></a></a> <div>Sets whether the plugin runs in verbose mode. As of plugin version 2.3, the default value is derived from Maven's global debug flag (compare command line switch <code>-X</code>). <br /> Starting with <b>3.0.0</b> the property has been renamed from <code>clean.verbose</code> to <code>maven.clean.verbose</code>.</div> - <ul> - -<li><b>Type</b>: <code>java.lang.Boolean</code></li> - -<li><b>Since</b>: <code>2.1</code></li> - -<li><b>Required</b>: <code>No</code></li> - -<li><b>User Property</b>: <code>maven.clean.verbose</code></li> - </ul> - </section></section> - </section> - - +<li><strong>Type</strong>: <code>java.lang.Boolean</code></li> +<li><strong>Since</strong>: <code>2.1</code></li> +<li><strong>Required</strong>: <code>No</code></li> +<li><strong>User Property</strong>: <code>maven.clean.verbose</code></li></ul></section></section></section> </main> </div> </div> @@ -462,7 +292,7 @@ <footer> <div class="container-fluid"> <div class="row-fluid"> - <p>© 2001–2023 + <p>© 2001–2024 <a href="https://www.apache.org/";>The Apache Software Foundation</a> </p> </div>
