I came across this really good article which talks about Maven build life cycle.
A Build Lifecycle is Made Up of Phases
Each of these build lifecycles is defined by a different list of build phases, wherein a build phase represents a stage in the lifecycle.
For example, the default lifecycle has the following build phases (for a complete list of the build phases, refer to the Lifecycle Reference):
validate
- validate the project is correct and all necessary information is availablecompile
- compile the source code of the projecttest
- test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployedpackage
- 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 runverify
- run any checks to verify the package is valid and meets quality criteriainstall
- install the package into the local repository, for use as a dependency in other projects locallydeploy
- done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.These build phases (plus the other build phases not shown here) are executed sequentially to complete the default lifecycle. Given the build phases above, this means that when the default lifecycle is used, Maven will first validate the project, then will try to compile the sources, run those against the tests, package the binaries (e.g. jar), run integration tests against that package, verify the package, install the verifed package to the local repository, then deploy the installed package in a specified environment.
To do all those, you only need to call the last build phase to be executed, in this case, deploy:
mvn deploy
That is because if you call a build phase, it will execute not only that build phase, but also every build phase prior to the called build phase.
source:http://stackoverflow.com/questions/1544619/if-i-run-mvn-deploy-does-it-build-new-artifacts-or-it-just-deploy-the-already-exi
Wednesday, April 21, 2010
Maven build lifecycle
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment