[maven-site] branch master updated: convention for CLI: no border nor line numbers

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new e951ca24 convention for CLI: no border nor line numbers
e951ca24 is described below

commit e951ca24ff4abf6614b96f48b8b1a7d6e3e3bc81
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Thu Jun 2 08:03:52 2022 +0200

    convention for CLI: no border nor line numbers
---
 content/apt/guides/getting-started/index.apt | 44 ++++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/content/apt/guides/getting-started/index.apt b/content/apt/guides/getting-started/index.apt
index 88990579..05555a60 100644
--- a/content/apt/guides/getting-started/index.apt
+++ b/content/apt/guides/getting-started/index.apt
@@ -239,9 +239,9 @@ my-app
  Change to the directory where pom.xml is created by archetype:generate and execute the following command to compile
  your application sources:
 
-+-----+
+-------
 mvn compile
-+-----+
+-------
 
  Upon executing this command you should see output like the following:
 
@@ -289,9 +289,9 @@ mvn compile
 
  Execute the following command:
 
-+----+
+------
 mvn test
-+----+
+------
 
  Upon executing this command you should see output like the following:
 
@@ -347,9 +347,9 @@ mvn test
 
  If you simply want to compile your test sources (but not execute the tests), you can execute the following:
 
-+----+
+------
  mvn test-compile
-+----+
+------
 
  Now that you can compile your application sources, compile your tests, and execute the tests, you'll want to move
  on to the next logical step so you'll be asking ...
@@ -360,9 +360,9 @@ mvn test
 
 ~~ How to skip tests ... jvz
 
-+----+
+------
 mvn package
-+----+
+------
 
  You can now take a look in the <<<$\{basedir\}/target>>> directory and you will see the generated JAR file.
 
@@ -371,9 +371,9 @@ mvn package
  {{{../introduction/introduction-to-repositories.html}Introduction to Repositories}} but let's move on to installing our artifact!
  To do so execute the following command:
 
-+----+
+------
 mvn install
-+----+
+------
 
  Upon executing this command you should see the following output:
 
@@ -454,15 +454,15 @@ mvn install
  a web site for your project! You will most likely want to customize your Maven site but if you're pressed for
  time all you need to do to provide basic information about your project is execute the following command:
 
-+----+
+------
 mvn site
-+----+
+------
 
   There are plenty of other standalone goals that can be executed as well, for example:
 
-+----+
+------
 mvn clean
-+----+
+------
 
   This will remove the <<<target>>> directory with all the build data before starting so that it is fresh.
 
@@ -711,9 +711,9 @@ application.version=${project.version}
  With that in place, you can execute the following command (process-resources is the build lifecycle phase where the resources are
  copied and filtered):
 
-+----+
+------
 mvn process-resources
-+----+
+------
 
  and the <<<application.properties>>> file under <<<target/classes>>> (and will eventually go into the jar) looks like this:
 
@@ -832,9 +832,9 @@ command.line.prop=${command.line.prop}
  Now, when you execute the following command (note the definition of the command.line.prop property on the command line), the
  <<<application.properties>>> file will contain the values from the system properties.
 
-+----+
+------
 mvn process-resources "-Dcommand.line.prop=hello again"
-+----+
+------
 
 
 * {How do I use external dependencies?}
@@ -1127,9 +1127,9 @@ mvn archetype:generate \
   Note the <<<\<packaging\>>>> element - this tells Maven to build as a WAR. Change into the webapp project's directory
   and try:
 
-+----+
+------
 mvn package
-+----+
+------
 
   You'll see <<<target/my-webapp.war>>> is built, and that all the normal steps were executed.
 
@@ -1202,9 +1202,9 @@ mvn package
 
   Now, try it... from the top level directory, run:
 
-+----+
+------
 mvn verify
-+----+
+------
 
   The WAR has now been created in <<<my-webapp/target/my-webapp.war>>>, and the JAR is included: