Plugin Details
This report describes goals, parameters details, requirements and sample usage of this plugin.
Goals
Goals available for this plugin:
| Goal | Description |
|---|---|
| site:attach-descriptor | Adds the site descriptor (site.xml) to the list of files to be installed/deployed.
For Maven-2.x this is enabled by default only when the project has This default execution has been removed from the built-in lifecycle of Maven 3.x for |
| site:auto-refresh | Renders the site once completely and then watches for Doxia source file changes. After modifications the affected file(s) are re-rendered and the output files updated. The goal blocks until the user presses Enter.
This is intended for use during site development to provide immediate feedback on changes. It only works on a single project and does neither consider child projects nor site staging. |
| site:deploy | Deploys the generated site using wagon supported protocols to the site URL specified in the <distributionManagement> section of the POM.
For |
| site:effective-site | Displays the effective site descriptor as an XML for this build, after inheritance and interpolation of site.xml, for the first locale. |
| site:help | Display help information on maven-site-plugin.
Call mvn site:help -Ddetail=true -Dgoal=<goal-name> to display parameter details. |
| site:jar | Bundles the site output into a JAR so that it can be deployed to a repository. |
| site:run | Starts the site up, rendering documents as requested for faster editing. It uses Jetty as the web server. See also: auto-refresh goal for automatic rerendering based on file system changes. |
| site:site | Generates the site for a single project.
Note that links between module sites in a multimodule build will not work, since local build directory structure doesn't match deployed site. |
| site:stage | Deploys the generated site to a local staging or mock directory based on the site URL specified in the <distributionManagement> section of the POM.
It can be used to test that links between module sites in a multi-module build work. This goal requires the site to already have been generated using the site goal, such as by calling |
| site:stage-deploy | Deploys the generated site to a staging or mock URL to the site URL specified in the <distributionManagement> section of the POM, using wagon supported protocols |
System Requirements
The following specifies the minimum requirements to run this Maven plugin:
| Maven | 3.6.3 |
| JDK | 1.8 |
System Requirements History
The following specifies the minimum requirements to run this Maven plugin for historical versions:
| Plugin Version | Maven | JDK |
|---|---|---|
| from 4.0.0-M15 to 4.0.0-M16 | 3.6.3 | 8 |
| from 4.0.0-M1 to 4.0.0-M14 | 3.2.5 | 8 |
| from 3.20.0 to 3.22.0 | 3.6.3 | 8 |
| from 3.12.0 to 3.12.1 | 3.2.5 | 8 |
| from 3.9.1 to 3.11.0 | 3.0.5 | 7 |
| from 3.8.2 to 3.9.0 | 3.0 | 7 |
| from 3.5 to 3.7.1 | 2.2.1 | 6 |
| from 3.1 to 3.4 | 2.2.1 | 5 |
| 3.0 | 2.2.0 | 5 |
| from 3.0-beta-1 to 3.0-beta-3 | 3.0 | 5 |
| from 2.2 to 2.4 | 2.2.0 | 5 |
| from 2.1 to 2.1.1 | 2.1.0 | 1.4 |
| from 2.0 to 2.0.1 | 2.0.6 | 1.4 |
| from 2.0-beta-6 to 2.0-beta-7 | 2.0.2 | 1.4 |
| 2.0-beta-5 | 2.0.2 | - |
| from 2.0-beta-1 to 2.0-beta-4 | - | - |
Usage
You should specify the version in your project's plugin configuration:
<project>
...
<build>
<!-- To define the plugin version in your parent POM -->
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>3.22.0</version>
</plugin>
...
</plugins>
</pluginManagement>
<!-- To use the plugin goals in your POM or parent POM -->
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
</plugin>
...
</plugins>
</build>
...
</project>
For more information, see "Guide to Configuring Plug-ins"

