You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2020/06/06 09:22:42 UTC
svn commit: r1878540 - in /maven/website/content:
guides/getting-started/index.html
guides/getting-started/maven-in-five-minutes.html
guides/getting-started/windows-prerequisites.html maven-site-1.0-site.jar
run.html
Author: svn-site-role
Date: Sat Jun 6 09:22:41 2020
New Revision: 1878540
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/guides/getting-started/index.html
maven/website/content/guides/getting-started/maven-in-five-minutes.html
maven/website/content/guides/getting-started/windows-prerequisites.html
maven/website/content/maven-site-1.0-site.jar
maven/website/content/run.html
Modified: maven/website/content/guides/getting-started/index.html
==============================================================================
--- maven/website/content/guides/getting-started/index.html (original)
+++ maven/website/content/guides/getting-started/index.html Sat Jun 6 09:22:41 2020
@@ -224,7 +224,8 @@ Vincent Siveton" />
<li><b>description</b> This element provides a basic description of your project. This is often used in Maven's generated documentation.</li></ul>
<p>For a complete reference of what elements are available for use in the POM please refer to our <a href="/ref/current/maven-model/maven.html">POM Reference</a>. Now let's get back to the project at hand.</p>
<p>After the archetype generation of your first project you will also notice that the following directory structure has been created:</p>
-<div class="source"><pre class="prettyprint linenums">my-app
+<div>
+<pre>my-app
|-- pom.xml
`-- src
|-- main
@@ -246,7 +247,8 @@ Vincent Siveton" />
<p>Change to the directory where pom.xml is created by archetype:generate and execute the following command to compile your application sources:</p>
<div class="source"><pre class="prettyprint linenums">mvn compile</pre></div>
<p>Upon executing this command you should see output like the following:</p>
-<div class="source"><pre class="prettyprint linenums">[INFO] ----------------------------------------------------------------------------
+<div>
+<pre>[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [compile]
[INFO] ----------------------------------------------------------------------------
@@ -275,7 +277,8 @@ Compiling 1 source file to <dir>/m
<p>Execute the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn test</pre></div>
<p>Upon executing this command you should see output like the following:</p>
-<div class="source"><pre class="prettyprint linenums">[INFO] ----------------------------------------------------------------------------
+<div>
+<pre>[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [test]
[INFO] ----------------------------------------------------------------------------
@@ -291,30 +294,16 @@ Compiling 1 source file to C:\Test\Maven
...
[INFO] [surefire:test]
[INFO] Setting reports dir: C:\Test\Maven2\test\my-app\target/surefire-reports
-
--------------------------------------------------------
- T E S T S
--------------------------------------------------------
-[surefire] Running com.mycompany.app.AppTest
-[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec
-
-Results :
-[surefire] Tests run: 1, Failures: 0, Errors: 0
-
-[INFO] ----------------------------------------------------------------------------
-[INFO] BUILD SUCCESSFUL
-[INFO] ----------------------------------------------------------------------------
-[INFO] Total time: 15 seconds
-[INFO] Finished at: Thu Oct 06 08:12:17 MDT 2005
-[INFO] Final Memory: 2M/8M
-[INFO] ----------------------------------------------------------------------------</pre></div>
+</pre></div>
+<p>T E S T S ------------------------------------------------------- [surefire] Running com.mycompany.app.AppTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0 sec</p></section></section><section>
+<h2><a name="Results_:_.5Bsurefire.5D_Tests_run:_1.2C_Failures:_0.2C_Errors:_0"></a>Results : [surefire] Tests run: 1, Failures: 0, Errors: 0</h2><figure><img src="INFO" alt="" /><figcaption>---------------------------------------------------------------------------- [INFO] BUILD SUCCESSFUL [INFO] ---------------------------------------------------------------------------- [INFO] Total time: 15 seconds [INFO] Finished at: Thu Oct 06 08:12:17 MDT 2005 [INFO] Final Memory: 2M/8M [INFO] ---------------------------------------------------------------------------- ----</figcaption></figure>
<p>Some things to notice about the output:</p>
<ul>
<li>Maven downloads more dependencies this time. These are the dependencies and plugins necessary for executing the tests (it already has the dependencies it needs for compiling and won't download them again).</li>
<li>Before compiling and executing the tests Maven compiles the main code (all these classes are up to date because we haven't changed anything since we compiled last).</li></ul>
<p>If you simply want to compile your test sources (but not execute the tests), you can execute the following:</p>
<div class="source"><pre class="prettyprint linenums"> mvn test-compile</pre></div>
-<p>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 ...</p></section><section>
+<p>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 ...</p><section>
<h3><a name="How_do_I_create_a_JAR_and_install_it_in_my_local_repository.3F"></a><a name="How_do_I_create_a_JAR_and_install_it_in_my_local_repository">How do I create a JAR and install it in my local repository?</a></h3>
<p>Making a JAR file is straight forward enough and can be accomplished by executing the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
@@ -322,7 +311,8 @@ Results :
<p>Now you'll want to install the artifact you've generated (the JAR file) in your local repository (<code>${user.home}/.m2/repository</code> is the default location). For more information on repositories you can refer to our <a href="../introduction/introduction-to-repositories.html">Introduction to Repositories</a> but let's move on to installing our artifact! To do so execute the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn install</pre></div>
<p>Upon executing this command you should see the following output:</p>
-<div class="source"><pre class="prettyprint linenums">[INFO] ----------------------------------------------------------------------------
+<div>
+<pre>[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [install]
[INFO] ----------------------------------------------------------------------------
@@ -334,28 +324,9 @@ Compiling 1 source file to <dir>/m
Compiling 1 source file to <dir>/my-app/target/test-classes
[INFO] [surefire:test]
[INFO] Setting reports dir: <dir>/my-app/target/surefire-reports
-
--------------------------------------------------------
- T E S T S
--------------------------------------------------------
-[surefire] Running com.mycompany.app.AppTest
-[surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.001 sec
-
-Results :
-[surefire] Tests run: 1, Failures: 0, Errors: 0
-
-[INFO] [jar:jar]
-[INFO] Building jar: <dir>/my-app/target/my-app-1.0-SNAPSHOT.jar
-[INFO] [install:install]
-[INFO] Installing <dir>/my-app/target/my-app-1.0-SNAPSHOT.jar to \
- <local-repository>/com/mycompany/app/my-app/1.0-SNAPSHOT/my-app-1.0-SNAPSHOT.jar
-[INFO] ----------------------------------------------------------------------------
-[INFO] BUILD SUCCESSFUL
-[INFO] ----------------------------------------------------------------------------
-[INFO] Total time: 5 seconds
-[INFO] Finished at: Tue Oct 04 13:20:32 GMT-05:00 2005
-[INFO] Final Memory: 3M/8M
-[INFO] ----------------------------------------------------------------------------</pre></div>
+</pre></div>
+<p>T E S T S ------------------------------------------------------- [surefire] Running com.mycompany.app.AppTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.001 sec</p></section></section><section>
+<h2><a name="Results_:_.5Bsurefire.5D_Tests_run:_1.2C_Failures:_0.2C_Errors:_0"></a>Results : [surefire] Tests run: 1, Failures: 0, Errors: 0</h2><figure><img src="INFO" alt="" /><figcaption>[jar:jar] [INFO] Building jar: <i>dir</i>/my-app/target/my-app-1.0-SNAPSHOT.jar [INFO] [install:install] [INFO] Installing <i>dir</i>/my-app/target/my-app-1.0-SNAPSHOT.jar to <br /><i>local-repository</i>/com/mycompany/app/my-app/1.0-SNAPSHOT/my-app-1.0-SNAPSHOT.jar [INFO] ---------------------------------------------------------------------------- [INFO] BUILD SUCCESSFUL [INFO] ---------------------------------------------------------------------------- [INFO] Total time: 5 seconds [INFO] Finished at: Tue Oct 04 13:20:32 GMT-05:00 2005 [INFO] Final Memory: 3M/8M [INFO] ---------------------------------------------------------------------------- ----</figcaption></figure>
<p>Note that the surefire plugin (which executes the test) looks for tests contained in files with a particular naming convention. By default the tests included are:</p>
<ul>
<li><code>**/*Test.java</code></li>
@@ -370,7 +341,7 @@ Results :
<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
<p>There are plenty of other standalone goals that can be executed as well, for example:</p>
<div class="source"><pre class="prettyprint linenums">mvn clean</pre></div>
-<p>This will remove the <code>target</code> directory with all the build data before starting so that it is fresh.</p></section><section>
+<p>This will remove the <code>target</code> directory with all the build data before starting so that it is fresh.</p><section>
<h3><a name="What_is_a_SNAPSHOT_version.3F"></a><a name="What_is_a_SNAPSHOT_version">What is a SNAPSHOT version?</a></h3>
<p>Notice the value of the <b>version</b> tag in the <code>pom.xml</code> file shown below has the suffix: <code>-SNAPSHOT</code>.</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
@@ -408,7 +379,8 @@ Results :
<h3><a name="How_do_I_add_resources_to_my_JAR.3F"></a><a name="How_do_I_add_resources_to_my_JAR">How do I add resources to my JAR?</a></h3>
<p>Another common use case that can be satisfied which requires no changes to the POM that we have above is packaging resources in the JAR file. For this common task, Maven again relies on the <a href="../introduction/introduction-to-the-standard-directory-layout.html">Standard Directory Layout</a>, which means by using standard Maven conventions you can package resources within JARs simply by placing those resources in a standard directory structure.</p>
<p>You see below in our example we have added the directory <code>${basedir}/src/main/resources</code> into which we place any resources we wish to package in our JAR. The simple rule employed by Maven is this: any directories or files placed within the <code>${basedir}/src/main/resources</code> directory are packaged in your JAR with the exact same structure starting at the base of the JAR.</p>
-<div class="source"><pre class="prettyprint linenums">my-app
+<div>
+<pre>my-app
|-- pom.xml
`-- src
|-- main
@@ -427,7 +399,8 @@ Results :
`-- app
`-- AppTest.java</pre></div>
<p>So you can see in our example that we have a <code>META-INF</code> directory with an <code>application.properties</code> file within that directory. If you unpacked the JAR that Maven created for you and took a look at it you would see the following:</p>
-<div class="source"><pre class="prettyprint linenums">|-- META-INF
+<div>
+<pre>|-- META-INF
| |-- MANIFEST.MF
| |-- application.properties
| `-- maven
@@ -440,13 +413,15 @@ Results :
`-- app
`-- App.class</pre></div>
<p>As you can see, the contents of <code>${basedir}/src/main/resources</code> can be found starting at the base of the JAR and our <code>application.properties</code> file is there in the <code>META-INF</code> directory. You will also notice some other files there like <code>META-INF/MANIFEST.MF</code> as well as a <code>pom.xml</code> and <code>pom.properties</code> file. These come standard with generation of a JAR in Maven. You can create your own manifest if you choose, but Maven will generate one by default if you don't. (You can also modify the entries in the default manifest. We will touch on this later.) The <code>pom.xml</code> and <code>pom.properties</code> files are packaged up in the JAR so that each artifact produced by Maven is self-describing and also allows you to utilize the metadata in your own application if the need arises. One simple use might be to retrieve the version of your application. Operating on the POM file would require you to use some Maven utilities
but the properties can be utilized using the standard Java API and look like the following:</p>
-<div class="source"><pre class="prettyprint linenums">#Generated by Maven
+<div>
+<pre>#Generated by Maven
#Tue Oct 04 15:43:21 GMT-05:00 2005
version=1.0-SNAPSHOT
groupId=com.mycompany.app
artifactId=my-app</pre></div>
<p>To add resources to the classpath for your unit tests, you follow the same pattern as you do for adding resources to the JAR except the directory you place resources in is ${basedir}/src/test/resources. At this point you would have a project directory structure that would look like the following:</p>
-<div class="source"><pre class="prettyprint linenums">my-app
+<div>
+<pre>my-app
|-- pom.xml
`-- src
|-- main
@@ -656,7 +631,7 @@ command.line.prop=${command.line.prop}</
</dependencies>
</project></pre></div>
<p>What about dependencies built somewhere else? How do they get into my local repository? Whenever a project references a dependency that isn't available in the local repository, Maven will download the dependency from a remote repository into the local repository. You probably noticed Maven downloading a lot of things when you built your very first project (these downloads were dependencies for the various plugins used to build the project). By default, the remote repository Maven uses can be found (and browsed) at <a class="externalLink" href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>. You can also set up your own remote repository (maybe a central repository for your company) to use instead of or in addition to the default remote repository. For more information on repositories you can refer to the <a href="../introduction/introduction-to-repositories.html">Introduction to Repositories</a>.</p>
-<p>Let's add another dependency to our project. Let's say we've added some logging to the code and need to add log4j as a dependency. First, we need to know what the groupId, artifactId, and version are for log4j. The appropriate directory on Maven Central is called /maven2/log4j/log4j. In that directory is a file called maven-metadata.xml. Here's what the maven-metadata.xml for log4j looks like:</p>
+<p>Let's add another dependency to our project. Let's say we've added some logging to the code and need to add log4j as a dependency. First, we need to know what the groupId, artifactId, and version are for log4j. The appropriate directory on Maven Central is called <a class="externalLink" href="https://repo.maven.apache.org/maven2/log4j/log4j/">/maven2/log4j/log4j</a>. In that directory is a file called maven-metadata.xml. Here's what the maven-metadata.xml for log4j looks like:</p>
<div class="source"><pre class="prettyprint linenums"><metadata>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
@@ -675,7 +650,7 @@ command.line.prop=${command.line.prop}</
</versions>
</versioning>
</metadata></pre></div>
-<p>From this file, we can see that the groupId we want is "log4j" and the artifactId is "log4j". We see lots of different version values to choose from; for now, we'll just use the latest version, 1.2.12 (some maven-metadata.xml files may also specify which version is the current release version). Alongside the maven-metadata.xml file, we can see a directory corresponding to each version of the log4j library. Inside each of these, we'll find the actual jar file (e.g. log4j-1.2.12.jar) as well as a pom file (this is the pom.xml for the dependency, indicating any further dependencies it might have and other information) and another maven-metadata.xml file. There's also an md5 file corresponding to each of these, which contains an MD5 hash for these files. You can use this to authenticate the library or to figure out which version of a particular library you may be using already.</p>
+<p>From this file, we can see that the groupId we want is "log4j" and the artifactId is "log4j". We see lots of different version values to choose from; for now, we'll just use the latest version, 1.2.12 (some maven-metadata.xml files may also specify which version is the current release version: see <a href="/ref/current/maven-repository-metadata/repository-metadata.html">repository metadata reference</a>). Alongside the maven-metadata.xml file, we can see a directory corresponding to each version of the log4j library. Inside each of these, we'll find the actual jar file (e.g. log4j-1.2.12.jar) as well as a pom file (this is the pom.xml for the dependency, indicating any further dependencies it might have and other information) and another maven-metadata.xml file. There's also an md5 file corresponding to each of these, which contains an MD5 hash for these files. You can use this to authenticate the library or to figure out which version of a particular library
you may be using already.</p>
<p>Now that we know the information we need, we can add the dependency to our pom.xml:</p>
<div class="source"><pre class="prettyprint linenums"><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -826,7 +801,8 @@ command.line.prop=${command.line.prop}</
<h3><a name="How_do_I_build_more_than_one_project_at_once.3F"></a><a name="How_do_I_build_more_than_one_project_at_once">How do I build more than one project at once?</a></h3>
<p>The concept of dealing with multiple modules is built in to Maven. In this section, we will show how to build the WAR above, and include the previous JAR as well in one step.</p>
<p>Firstly, we need to add a parent <code>pom.xml</code> file in the directory above the other two, so it should look like this:</p>
-<div class="source"><pre class="prettyprint linenums">+- pom.xml
+<div>
+<pre>+- pom.xml
+- my-app
| +- pom.xml
| +- src
@@ -878,7 +854,8 @@ command.line.prop=${command.line.prop}</
<p>Now, try it... from the top level directory, run:</p>
<div class="source"><pre class="prettyprint linenums">mvn verify</pre></div>
<p>The WAR has now been created in <code>my-webapp/target/my-webapp.war</code>, and the JAR is included:</p>
-<div class="source"><pre class="prettyprint linenums">$ jar tvf my-webapp/target/my-webapp-1.0-SNAPSHOT.war
+<div>
+<pre>$ jar tvf my-webapp/target/my-webapp-1.0-SNAPSHOT.war
0 Fri Jun 24 10:59:56 EST 2005 META-INF/
222 Fri Jun 24 10:59:54 EST 2005 META-INF/MANIFEST.MF
0 Fri Jun 24 10:59:56 EST 2005 META-INF/maven/
Modified: maven/website/content/guides/getting-started/maven-in-five-minutes.html
==============================================================================
--- maven/website/content/guides/getting-started/maven-in-five-minutes.html (original)
+++ maven/website/content/guides/getting-started/maven-in-five-minutes.html Sat Jun 6 09:22:41 2020
@@ -143,9 +143,11 @@
<h3><a name="Installation"></a>Installation</h3>
<p><i>Maven is a Java tool, so you must have <a class="externalLink" href="https://www.oracle.com/technetwork/java/javase/downloads/index.html">Java</a> installed in order to proceed.</i></p>
<p>First, <a href="../../download.html">download Maven</a> and follow the <a href="../../install.html">installation instructions</a>. After that, type the following in a terminal or in a command prompt:</p>
-<div class="source"><pre class="prettyprint linenums">mvn --version</pre></div>
+<div>
+<pre>mvn --version</pre></div>
<p>It should print out your installed version of Maven, for example:</p>
-<div class="source"><pre class="prettyprint linenums">Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
+<div>
+<pre>Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: D:\apache-maven-3.6.3\apache-maven\bin\..
Java version: 1.8.0_232, vendor: AdoptOpenJDK, runtime: C:\Program Files\AdoptOpenJDK\jdk-8.0.232.09-hotspot\jre
Default locale: en_US, platform encoding: Cp1250
@@ -154,12 +156,15 @@ OS name: "windows 10", version
<p><b>If you are using Windows, you should look at</b> <a href="./windows-prerequisites.html">Windows Prerequisites</a> <b>to ensure that you are prepared to use Maven on Windows.</b></p></section><section>
<h3><a name="Creating_a_Project"></a>Creating a Project</h3>
<p>You will need somewhere for your project to reside, create a directory somewhere and start a shell in that directory. On your command line, execute the following Maven goal:</p>
-<div class="source"><pre class="prettyprint linenums">mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false</pre></div>
+<div>
+<pre>mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false</pre></div>
<p><i>If you have just installed Maven, it may take a while on the first run. This is because Maven is downloading the most recent artifacts (plugin jars and other files) into your local repository. You may also need to execute the command a couple of times before it succeeds. This is because the remote server may time out before your downloads are complete. Don't worry, there are ways to fix that.</i></p>
<p>You will notice that the <i>generate</i> goal created a directory with the same name given as the artifactId. Change into that directory.</p>
-<div class="source"><pre class="prettyprint linenums">cd my-app</pre></div>
+<div>
+<pre>cd my-app</pre></div>
<p>Under this directory you will notice the following <a href="../introduction/introduction-to-the-standard-directory-layout.html">standard project structure</a>.</p>
-<div class="source"><pre class="prettyprint linenums">my-app
+<div>
+<pre>my-app
|-- pom.xml
`-- src
|-- main
@@ -202,9 +207,11 @@ OS name: "windows 10", version
<h4><a name="What_did_I_just_do.3F"></a>What did I just do?</h4>
<p>You executed the Maven goal <i>archetype:generate</i>, and passed in various parameters to that goal. The prefix <i>archetype</i> is the <a href="../../plugins/index.html">plugin</a> that provides the goal. If you are familiar with <a class="externalLink" href="http://ant.apache.org">Ant</a>, you may conceive of this as similar to a task. This <i>archetype:generate</i> goal created a simple project based upon a <a href="/archetypes/maven-archetype-quickstart/">maven-archetype-quickstart</a> archetype. Suffice it to say for now that a <i>plugin</i> is a collection of <i>goals</i> with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".</p></section><section>
<h4><a name="Build_the_Project"></a>Build the Project</h4>
-<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
+<div>
+<pre>mvn package</pre></div>
<p>The command line will print out various actions, and end with the following:</p>
-<div class="source"><pre class="prettyprint linenums"> ...
+<div>
+<pre> ...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
@@ -220,9 +227,11 @@ OS name: "windows 10", version
<li>process-resources</li>
<li>compile</li></ol>
<p>You may test the newly compiled and packaged JAR with the following command:</p>
-<div class="source"><pre class="prettyprint linenums">java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App</pre></div>
+<div>
+<pre>java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App</pre></div>
<p>Which will print the quintessential:</p>
-<div class="source"><pre class="prettyprint linenums">Hello World!</pre></div></section></section><section>
+<div>
+<pre>Hello World!</pre></div></section></section><section>
<h3><a name="Java_9_or_later"></a>Java 9 or later</h3>
<p>By default your version of Maven might use an old version of the <code>maven-compiler-plugin</code> that is not compatible with Java 9 or later versions. To target Java 9 or later, you should at least use version 3.6.0 of the <code>maven-compiler-plugin</code> and set the <code>maven.compiler.release</code> property to the Java release you are targetting (e.g. 9, 10, 11, 12, etc.).</p>
<p>In the following example, we have configured our Maven project to use version 3.8.1 of <code>maven-compiler-plugin</code> and target Java 11:</p>
@@ -261,10 +270,12 @@ OS name: "windows 10", version
<li><b>site</b>: generates site documentation for this project</li></ul>
<p>Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, <i>package</i> executes <i>jar:jar</i> if the project type is a JAR, and <i>war:war</i> if the project type is - you guessed it - a WAR.</p>
<p>An interesting thing to note is that phases and goals may be executed in sequence.</p>
-<div class="source"><pre class="prettyprint linenums">mvn clean dependency:copy-dependencies package</pre></div>
+<div>
+<pre>mvn clean dependency:copy-dependencies package</pre></div>
<p>This command will clean the project, copy dependencies, and package the project (executing all phases up to <i>package</i>, of course).</p></section><section>
<h4><a name="Generating_the_Site"></a>Generating the Site</h4>
-<div class="source"><pre class="prettyprint linenums">mvn site</pre></div>
+<div>
+<pre>mvn site</pre></div>
<p>This phase generates a site based upon information on the project's pom. You can look at the documentation generated under <code>target/site</code>.</p></section></section><section>
<h3><a name="Conclusion"></a>Conclusion</h3>
<p>We hope this quick overview has piqued your interest in the versatility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the <a href="./index.html">Maven Getting Started Guide</a>.</p></section></section>
Modified: maven/website/content/guides/getting-started/windows-prerequisites.html
==============================================================================
--- maven/website/content/guides/getting-started/windows-prerequisites.html (original)
+++ maven/website/content/guides/getting-started/windows-prerequisites.html Sat Jun 6 09:22:41 2020
@@ -128,7 +128,8 @@
<h3><a name="Prerequisites"></a>Prerequisites</h3>
<p>Maven is written in Java (and primarily used to build Java programs). Thus, the major prerequisite is the Java SDK. You need to install the Java SDK (e.g. from <a class="externalLink" href="https://www.oracle.com/technetwork/java/javase/downloads/index.html">Oracle's download site</a>).</p>
<p>Once Java is installed, you must ensure that the commands from the Java SDK are in your PATH environment variable. Running, for example,</p>
-<div class="source"><pre class="prettyprint linenums">java -version</pre></div>
+<div>
+<pre>java -version</pre></div>
<p>must show the right version number.</p></section><section>
<h3><a name="Maven_Unpacked"></a>Maven Unpacked</h3>
<p>You need to unpack the Maven distribution. Don't unpack it in the middle of your source code; pick some location and unpack it there. Let's assume that the path is <code>${maven.home}</code>.</p></section><section>
Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: maven/website/content/run.html
==============================================================================
--- maven/website/content/run.html (original)
+++ maven/website/content/run.html Sat Jun 6 09:22:41 2020
@@ -151,7 +151,7 @@ The syntax for running Maven is as follo
<div class="source"><pre class="prettyprint linenums">mvn [options] [<goal(s)>] [<phase(s)>]
</pre></div></div>
-<p>All available options are documented in the built in help that you can access with</p>
+<p>All available options are documented in the built-in help that you can access with</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn -h
@@ -163,7 +163,7 @@ The syntax for running Maven is as follo
<div class="source"><pre class="prettyprint linenums">mvn package
</pre></div></div>
-<p>The built in life cycles and their phases are in order are:</p>
+<p>The built-in lifecycles and their phases are in order are:</p>
<ul>
<li>
@@ -192,7 +192,7 @@ The syntax for running Maven is as follo
</pre></div></div>
<p>This is the most common build invocation for a Maven project.</p>
-<p>When not working with a project, and in some other use cases, you might want to invoke a specific task implemented by a part of Maven - this is called a goal of a plugin. E.g.:</p>
+<p>When not working with a project, and in some other use cases, you might want to invoke a specific task implemented by a part of Maven - this is called a <b>goal</b> of a plugin. E.g.:</p>
<div class="source">
<div class="source"><pre class="prettyprint linenums">mvn archetype:generate