The commons:download-page
goal generates a custom Download page for the latest release of a component.
Execute the goal using the following command:
mvn commons:download-page
The above command generates an xdoc page named download_componentid.xml in either the xdocs
or src/site/xdoc
directory (depending on which exists), which should be checked into subversion.
This will cause a download_componentid.html page to be generated when the mvn site
is run.
Remember to add a Download link to download_componentid.cgi to the maven site.xml
.
Note: The Download page should only need to be re-generated after a new release of the component or if the download page template changes.
This goal uses the following:
download-page
mojo defintion in the
generate-xdocs.mojos.xml mapping documentdownload-page
target in
generate-xdocs.build.xml
ant scriptcommons.release.version
property is set or not.
To generate a Download page, the following properties are configured in the component's pom.xml
-bin
) The suffix for the binary release
(some components use "-bin", others have no suffix)Example configuration for Commons Chain:
<properties> <commons.componentid>chain</commons.componentid> <commons.release.version>1.2</commons.release.version> </properties>
Sometimes there is a requirement to list two versions on the download page. This can be achieved using the following properties:
-bin
) The suffix for the alternative
binary release (some components use "-bin", others have no suffix)Example configuration for Commons DBCP with two releases:
<properties> <commons.componentid>dbcp</commons.componentid> <commons.release.version>1.4</commons.release.version> <commons.release.desc>for JDBC 4 (JDK 1.6)</commons.release.desc> <commons.release.2.version>1.3</commons.release.2.version> <commons.release.2.desc> for JDBC 3 (JDK 1.4-1.5)</commons.release.2.desc> </properties>
The above configuration generates a download page for two releases shown below: