What is the correct order of Maven phases from first to last?

• A. compile, validate, test, package, verify, install, deploy
• B. package, validate, compile, test, verify, install, deploy
• C. validate, compile, test, package, verify, install, deploy
• D. validate, compile, package, test, verify, install, deploy

Answer: (C)

Maven builds follow a fixed sequence of phases in the default lifecycle. The first phase is validate, which checks that the project is correct and that the POM can be processed. Next is compile, where the source code is compiled. Then comes test, which runs the unit tests against the compiled code. After successful tests, packaging creates the final deliverable (like a jar or war). The verify phase then performs any checks to ensure the package is valid. Install adds the artifact to the local repository, making it available for other local projects. Finally, deploy publishes the artifact to a remote repository for sharing.

This order is why the shown sequence is correct: validate, then compile, then test, then package, then verify, then install, then deploy. The other options place steps in an order that violates the logical flow—packaging before tests, or compiling before validation, for example—so they don’t align with how Maven builds are designed to proceed.