THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Command | Description | Notes |
|---|---|---|
| mvn clean | removes all the files created by the previous build | Usually means it deletes the contents of the modules */target/ directory. |
| mvn validate | validates that the maven poms are all correct and that no config is missing | Usefull to run when making build modifications to ensure consistency. |
| mvn compile | compiles the source code of the project | This will verify that project dependencies are correct. |
| mvn test | executes the unit tests | Should not rely on code being packaged or deployed, only unit tests. |
mvn package | packages the code into the its distributable formats (jar, war, zip etc) | Each pom specifies what the distribution format is, default is POM. |
| mvn verify | verifies that the packaged code is valid | This will run the integration and system tests. |
| mvn install | installs the package into the local maven repository | This will result in the module being available, locally, as a depedency |
| mvn deploy | copies the final artifacts to the remote maven repository for sharing | This would happen only when modules ready to be shared with other developers or projects |
| mvn site:stage | creates a staged version of the maven site with all the reports | Staging output defaults to the */target/staging/ directory |
| mvn jacoco:report | generates the code coverage report for the tests that have been executed | Test output appears in the */target/site/jacoco/ directory |
...