Maven2 life cycle

Maven2 phase (life cycle) description:
Maven2 has three independent life cycles, and Maven commands are also based on these life cycles.
1.clean: Clean up previously built components, which are divided into the following three sub-stages:
  a.pre-clean Perform some work that needs to be done before cleaning.
  b.clean clean up the files generated by the last build
  c.post-clean perform some work that needs to be done after
cleaning The phases are as follows:
  a.validate verify the project is correct and all required information is available
  b.initialize initialize the build state
  c.generate-sources generate all the source code used for compilation
  d.process-sources process the source code
  e .generate-resources Generate the resources contained in the package
  f.process-resources Copy and process the resources to the target directory, ready for packaging
  g.compile Compile the main source code of the project
  h.process-classes Perform the files generated by the compiler Post-processing
  i.generate-test-sources Generates all test source code for compilation
  j.process-test-sources Processes test source code
  k.generate-test-resources Resources needed to create tests
  l.process-test-resources Copy and process resources to the test target directory
  m.compile Compile the test source code to the target directory
  n.process-test-classes Post-process the files generated by compiling the test source code
  o.test Use the appropriate unit The test framework runs tests that should not be packaged or deployed
  p.prepare-package does everything needed to prepare it for packaging, which often results in a processed version of the package that has not been packaged
  q.package uses the set way to package the compiled files
  r.pre-integration-test perform some necessary operations before the execution of the integration test
  s.integration-test process and deploy the package to the integration test environment for testing
  t.post-integration-test to integrate Tests are post-processed
  u.verify performs all checks to ensure the package is correct and meets quality requirements
  v.install installs the package to the local repository, provides dependencies for other local projects i
  w.deploy publishes the package, copies the final package to the remote repository 3.site
: Build and publish project site
  a.pre-site Pre-preparation
  b.site Generate project site documentation
  c.post-site Post-processing
  d.site-deploy Deploy site to server

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=327019691&siteId=291194637