Table of Contents
Abstract
This chapter describes how to perform a release, and to deploy that release remotely. It will only be of interest to contributors with admin privileges to release and deploy code.
The release process tags the codebase under
trunk into tags, updating the
versions in all POMs in the process removing the
"-SNAPSHOT" suffix. After the release is finished, it may then be
deployed . Note that snapshots do not go through this process and can be
deployed at any time (see Chapter 9, Deploying a Code Snapshot).
The release is performed in two parts: first the main artifacts, then the support artifacts.
First, ensure there are no oustanding code changes.
Then, perform a smoke test:
As per Chapter 3, Building Projects from Source, build the parent, the main artifacts and the support artifacts from source
make sure that the archetype runs correctly
make sure that the documentation is built correctly
make sure that the site builds correctly
To check the site builds it is actually necessary to perform a local deploy. See Section 8.6, “Checking the Site by Deploying it Locally” for details.d
Finally, if the release is to be deployed remotely (as is typically the case), check the server settings are defined (see Appendix A, Deployment Prerequisites).