svn commit: r1875335 - in /maven/website/content: configure.html maven-site-1.0-site.jar

[sv...@apache.org]

Author: svn-site-role
Date: Tue Mar 17 23:30:57 2020
New Revision: 1875335

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/configure.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/configure.html
==============================================================================
--- maven/website/content/configure.html (original)
+++ maven/website/content/configure.html Tue Mar 17 23:30:57 2020
@@ -149,11 +149,11 @@ The configuration for Apache Maven usage
 in a number of places: 
 <section>
 <h2><a name="MAVEN_OPTS_environment_variable:"></a><code>MAVEN_OPTS</code> environment variable:</h2>
-<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to globally to Maven. E.g. JVM memory settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
+<p>This variable contains parameters used to start up the JVM running Maven and can be used to supply additional options to it. E.g. JVM memory settings could be defined with the value <code>-Xms256m -Xmx512m</code>.</p></section><section>
 <h2><a name="settings.xml_file:"></a><code>settings.xml</code> file:</h2>
 <p>Located in USER_HOME/.m2 the settings files is designed to contain any configuration for Maven usage across projects.</p></section><section>
 <h2><a name="a.mvn_folder:"></a><code>.mvn</code> folder:</h2>
-<p>Located with in the projects top level folder, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code> contain project specific configuration for running Maven.</p>
+<p>Located within the project&#x2019;s top level directory, the files <code>maven.config</code>, <code>jvm.config</code>, and <code>extensions.xml</code> contain project specific configuration for running Maven.</p>
 <p>This folder is part of the project and may be checked in into your version control.</p><section>
 <h3><a name="a.mvn.2Fextensions.xml_file:"></a><code>.mvn/extensions.xml</code> file:</h3>
 <p>The old way (up to Maven 3.2.5) was to create a jar (must be shaded if you have other dependencies) which contains the extension and put it manually into the <code>${MAVEN_HOME}/lib/ext</code> folder. This means you had to change the Maven installation. The consequence was that everyone who likes to use this needed to change it&#x2019;s installation and makes the on-boarding for a developer much more inconvenient. The other option was to give the path to the jar on command line via <code>mvn -Dmaven.ext.class.path=extension.jar</code>. This has the drawback giving those options to your Maven build every time you are calling Maven. Not very convenient as well.</p>
@@ -181,7 +181,7 @@ in a number of places:
 <div class="source"><pre class="prettyprint linenums">    -Xmx2048m -Xms1024m -XX:MaxPermSize=512m -Djava.awt.headless=true
 </pre></div></div>
 
-<p>You don&#x2019;t need to remember of using this options in <code>MAVEN_OPTS</code> or switching between different configurations. in the end, add the following:</p></section></section><section>
+<p>You don&#x2019;t need to use these options in <code>MAVEN_OPTS</code> or switch between different configurations.</p></section></section><section>
 <h2><a name="Other_guides"></a>Other guides</h2>
 <p>The following guides contain further information to specific configuration aspects:</p>
 <ul>

Modified: maven/website/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.