Maven Default Lifecycle Phases

Direct Answer

Important default-lifecycle phases in order include validate, compile, test, package, verify, install, and deploy, with other phases between them. Invoking a phase runs earlier phases in that lifecycle, but actual work depends on plugin goals bound by the packaging and POM. verify runs integration tests only when a plugin such as Failsafe is configured for the relevant phases.

Code Example

mvn compile   # visits phases through compile
mvn test      # also visits compile and test-compile
mvn package   # also visits test, then runs the packaging goal bound for the project type
mvn verify    # runs configured goals through verify; integration tests require bindings
mvn install   # stores the artifact/POM in the local Maven repository
mvn deploy    # publishes to the configured remote deployment repository

For ordinary jar packaging Maven supplies useful default bindings, but a lifecycle phase does not guarantee a particular goal in every project.

Common Mistakes & Pitfalls

• Running phases individually: Freshers often run 'mvn compile' then 'mvn test' then 'mvn package' as three separate commands, not realizing that 'mvn package' visits earlier phases, where configured/default goals compile and test. This wastes time and shows a misunderstanding of how phases work.
• Confusing install with deployment: Many freshers think 'mvn install' deploys their application to a server. It actually just copies the JAR to your local ~/.m2/repository directory so other Maven projects on your machine can use it as a dependency. Deploying to a server is done by tools like Docker or Kubernetes, not Maven install.
• Skipping to package without understanding: Running 'mvn package' without understanding that it's visiting the test phase and running its bound goals unless tests are skipped can be dangerous. If tests fail, the build fails — some freshers then disable tests entirely rather than fixing the failing test, which defeats the purpose of automated testing.