deploy: done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.install: install the package into the local repository, for use as a dependency in other projects locally.verify: run any checks to verify the package is valid and meets quality criteria.integration-test: process and deploy the package if necessary into an environment where integration tests can be run.package: take the compiled code and package it in its distributable format, such as a JAR.These tests should not require the code be packaged or deployed test: test the compiled source code using a suitable unit testing framework.compile: compile the source code of the project.validate: validate the project is correct and all necessary information is available.Running Maven Tools Maven PhasesĪlthough hardly a comprehensive list, these are the most common default lifecycle phases executed. To learn more about javac's -release option, see JEP 247. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items". Suffice it to say for now that a plugin is a collection of goals with a general common purpose. This archetype:generate goal created a simple project based upon a maven-archetype-quickstart archetype. If you are familiar with Ant, you may conceive of this as similar to a task. The prefix archetype is the plugin that provides the goal. You executed the Maven goal archetype:generate, and passed in various parameters to that goal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |