From 586c511cc9140f4faa1aba1b996290c16bac437a Mon Sep 17 00:00:00 2001 From: Chas Honton Date: Fri, 6 May 2016 21:23:11 -0700 Subject: [PATCH] fix formatting of introduction-to-the-lifecycle --- .../guides/introduction/introduction-to-the-lifecycle.apt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt index b97f7a18fb..bcd3d5b643 100644 --- a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt +++ b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt @@ -90,14 +90,16 @@ Introduction to the Build Lifecycle ** {Usual Command Line Calls} In a development environment, use the following call to build and install artifacts into the local repository. + ------ mvn install ------ This command executes each default life cycle phase in order (<<>>, <<>>, <<>>, etc.), - before executing <<>. You only need to call the last build phase to be executed, in this case, <<>>: + before executing <<>>. You only need to call the last build phase to be executed, in this case, <<>>: In a build environment, use the following call to cleanly build and deploy artifacts into the shared repository. + ------ mvn clean deploy ------ @@ -151,7 +153,7 @@ mvn clean dependency:copy-dependencies package to the <<>> phase to collect coverage statistics or decommission the integration test container. Failsafe and code coverage plugins bind goals to <<>> and <<>> phases. The net result is - test and coverage reports are available after the <<>> phase. If <> were to be called from the + test and coverage reports are available after the <<>> phase. If <<>> were to be called from the command line, no reports are generated. Worse is that the integration test container environment is left in a hanging state; the Tomcat webserver or Docker instance is left running, and Maven may not even terminate by itself.