Whether to add a schema to the POM if it was previously missing on release.

Additional arguments to pass to the Maven executions, separated by spaces.

Whether to automatically assign submodules the parent version. If set to false, the user will be prompted for the version of each submodules.

The branch base directory in SVN, you must define it if you don't use the standard svn layout (trunk/tags/branches). For example, http://svn.apache.org/repos/asf/maven/plugins/branches. The URL is an SVN URL and does not include the SCM provider and protocol.

The branch name to use.

Command-line version of checkModificationExcludes.

A list of additional exclude filters that will be skipped when checking for modifications on the working copy. Is ignored, when checkModificationExcludes is set.

Specify the new version for the working copy. This parameter is only meaningful if updateWorkingCopyVersions = true.

Dry run: don't checkin or tag anything in the scm repository, or modify the checkout. Running mvn -DdryRun=true release:prepare is useful in order to check that modifications to poms and scm operations (only listed on the console) are working as expected. Modified POMs are written alongside the originals without modifying them.

The JAVA_HOME parameter to use for forked Maven invocations.

The command-line local repository directory in use for this build (if specified).

Role hint of the MavenExecutor implementation to use.

The M2_HOME parameter to use for forked Maven invocations.

The SCM password to use.

Currently only implemented with svn scm. Enable the --pin-externals option in svn copy command which is new in Subversion 1.9.

The file name of the POM to execute any goals against. As of version 3.0.0, this defaults to the name of POM file of the project being built.

The role-hint for the NamingPolicy implementation used to calculate the project names.

The role-hint for the VersionPolicy implementation used to calculate the project versions.

Add a new or overwrite the default implementation per provider. The key is the scm prefix and the value is the role hint of the ScmProvider.

Implemented with git will or not push changes to the upstream repository. true by default to preserve backward compatibility.

The role-hint for the Strategy implementation used to specify the phases per goal.

Specify the new version for the branch. This parameter is only meaningful if updateBranchVersions = true.

currently only implemented with svn scm. Enable a workaround to prevent issue due to svn client > 1.5.0 (https://issues.apache.org/jira/browse/SCM-406)

The SCM commit comment when branching. Defaults to "@{prefix} prepare branch @{releaseLabel}".

Property interpolation is performed on the value, but in order to ensure that the interpolation occurs during release, you must use @{...} to reference the properties rather than ${...}. The following properties are available:

• prefix - The comment prefix.
• groupId - The groupId of the root project.
• artifactId - The artifactId of the root project.
• releaseLabel - The release version of the root project.

The message prefix to use for all SCM changes.

Whether to suppress a commit of changes to the working copy before the tag is created.

This requires remoteTagging to be set to false.

suppressCommitBeforeBranch is useful when you want to avoid poms with released versions in all revisions of your trunk or development branch.

The SCM tag to use.

The tag base directory in SVN, you must define it if you don't use the standard svn layout (trunk/tags/branches). For example, http://svn.apache.org/repos/asf/maven/plugins/tags. The URL is an SVN URL and does not include the SCM provider and protocol.

Format to use when generating the tag name if none is specified. Property interpolation is performed on the tag, but in order to ensure that the interpolation occurs during release, you must use @{...} to reference the properties rather than ${...}. The following properties are available:

• groupId or project.groupId - The groupId of the root project.
• artifactId or project.artifactId - The artifactId of the root project.
• version or project.version - The release version of the root project.

Whether to update versions in the branch.

Whether to update dependencies version to the next development version.

Whether to update versions to SNAPSHOT in the branch.

Whether to update versions in the working copy.

Whether to use "edit" mode on the SCM, to lock the file for editing during SCM operations.

The SCM username to use.

A workItem for SCMs like RTC, TFS etc, that may require additional information to perform a pushChange operation.