Lifecycle

validate	validate the project is correct and all necessary information is available
compile	compile the source code of the project
test	test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed
package	take the compiled code and package it in its distributable format, such as a JAR
integration-test	process and deploy the package if necessary into an environment where integration tests can be run
verify	run any checks to verify the package is valid and meets quality criteria
install	install the package into the local repository, for use as a dependency in other projects locally
deploy	done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects

Lifecycle

compile	this is the default scope, used if none is specified. Compile dependencies are available in all classpaths. Furthermore, those dependencies are propagated to dependent projects.
provided	this is much like compile, but indicates you expect the JDK or a container to provide it at runtime. It is only available on the compilation and test classpath, and is not transitive.
runtime	this scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath.
test	this scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases.
system	this scope is similar to `provided` except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository.

Specify projects

--projects	-pl	Comma-delimited list of specified reactor projects to build instead of all projects. A project can be specified by [groupId]:artifactId or by its relative path.
--resume-from	-rf	Resume reactor from specified project
--activate-profiles	-P	Comma-delimited list of profiles to activate
--non-recursive	-N	Do not recurse into sub-projects
--also-make	-am	If project list is specified, also build projects required by the list
--also-make-dependents	-amd	If project list is specified, also build projects that depend on projects on the list

Main

--threads	-T	Thread count, for instance 2.0C where C is core multiplied
--define	-D	Define a system property
--batch-mode	-B	Run in non-interactive (batch) mode
--builder	-b	The id of the build strategy to use.

Output

--quiet	-q	Quiet output - only show errors
--errors	-e	Produce execution error messages
--debug	-X	Produce execution debug output

Repo

--update-snapshots	-U	Forces a check for missing releases and updated snapshots on remote repositories
--offline	-o	Work offline
--no-snapshot-updates	-nsu	Suppress SNAPSHOT updates
--legacy-local-repository	-llr	Use Maven 2 Legacy Local Repository behaviour, ie no use of \_remote.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true

Passwords

--encrypt-master-password	-emp	Encrypt master security password
--encrypt-password	-ep	Encrypt server password

Fail

--fail-at-end	-fae	Only fail the build afterwards; allow all non-impacted builds to continue
--fail-fast	-ff	Stop at first failure in reactorized builds
--fail-never	-fn	NEVER fail the build, regardless of project result

Checksum

--lax-checksums	-c	Warn if checksums don't match
--strict-checksums	-C	Fail the build if checksums don't match

File locations

--file	-f	Force the use of an alternate POM file (or directory with pom.xml).
--settings	-s	Alternate path for the user settings file
--toolchains	-t	Alternate path for the user toolchains file
--log-file	-l	Log file to where all build output will go.
--global-settings	-gs	Alternate path for the global settings file
--global-toolchains	-gt	Alternate path for the global toolchains file

Version/Misc

--version	-v	Display version information
--show-version	-V	Display version information WITHOUT stopping build
--help	-h	Display help information

Deprecated options

--check-plugin-updates	-cpu	Ineffective, only kept for backward compatibility
--update-plugins	-up	Ineffective, only kept for backward compatibility
--no-plugin-registry	-npr	Ineffective, only kept for backward compatibility
--no-plugin-updates	-npu	Ineffective, only kept for backward compatibility