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 2019/06/09 13:59:37 UTC
svn commit: r1860906 [13/22] - in /maven/website/content: ./
apache-resource-bundles/ archives/maven-2.x/ background/ developers/
developers/conventions/ developers/release/ developers/website/ docs/
docs/2.0.1/ docs/2.0.10/ docs/2.0.11/ docs/2.0.2/ do...
Modified: maven/website/content/guides/mini/guide-deployment-security-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-deployment-security-settings.html (original)
+++ maven/website/content/guides/mini/guide-deployment-security-settings.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-deployment-security-settings.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-deployment-security-settings.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,9 +160,9 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Security_and_Deployment_Settings"></a>Security and Deployment Settings</h2>
-<p>Repositories to deploy to are defined in a project in the <tt>distributionManagement</tt> section. However, you cannot put your username, password, or other security settings in that project. For that reason, you should add a server definition to your own settings with an id that matches that of the deployment repository in the project.</p>
+<p>Repositories to deploy to are defined in a project in the <code>distributionManagement</code> section. However, you cannot put your username, password, or other security settings in that project. For that reason, you should add a server definition to your own settings with an id that matches that of the deployment repository in the project.</p>
<p>In addition, some repositories may require authorisation to download from, so the corresponding settings can be specified in a server element in the same way.</p>
<p>Which settings are required will depend on the type of repository you are deploying to. As of the first release, only SCP deployments and file deployments are supported by default, so only the following SCP configuration is needed:</p>
<div class="source"><pre class="prettyprint linenums">
@@ -185,7 +185,7 @@
</settings>
</pre></div>
<p>To encrypt passwords in these sections, refer to <a href="./guide-encryption.html"> Encryption Settings</a>.</p>
-<p><b>Note</b>: The settings descriptor documentation can be found on the <a href="../../maven-settings/settings.html">Maven Local Settings Model Website</a>.</p></div>
+<p><b>Note</b>: The settings descriptor documentation can be found on the <a href="../../maven-settings/settings.html">Maven Local Settings Model Website</a>.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-encryption.html
==============================================================================
--- maven/website/content/guides/mini/guide-encryption.html (original)
+++ maven/website/content/guides/mini/guide-encryption.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-encryption.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-encryption.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -161,15 +161,14 @@ Robert Scholte" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Password_Encryption">Password Encryption</a></h2>
<ol style="list-style-type: decimal">
<li><a href="#Introduction">Introduction</a></li>
<li><a href="#How_to_create_a_master_password">How to create a master password</a></li>
<li><a href="#How_to_encrypt_server_passwords">How to encrypt server passwords</a></li>
<li><a href="#How_to_keep_the_master_password_on_removable_drive">How to keep the master password on removable drive</a></li>
-<li><a href="#Tips">Tips</a></li></ol>
-<div class="section">
+<li><a href="#Tips">Tips</a></li></ol><section>
<h3><a name="Introduction">Introduction</a></h3>
<p>Maven 2.1.0+ now supports server password encryption. The main use case, addressed by this solution is:</p>
<ul>
@@ -177,37 +176,35 @@ Robert Scholte" />
<li>some users have the privilege to deploy Maven artifacts to repositories, some don't.
<ul>
<li>this applies to any server operations, requiring authorization, not only deployment</li></ul></li>
-<li><tt>settings.xml</tt> is shared between users</li></ul>
+<li><code>settings.xml</code> is shared between users</li></ul>
<p>The implemented solution adds the following capabilities:</p>
<ul>
-<li>authorized users have an additional <tt>settings-security.xml</tt> file in their <tt>${user.home}/.m2</tt> folder
+<li>authorized users have an additional <code>settings-security.xml</code> file in their <code>${user.home}/.m2</code> folder
<ul>
<li>this file either contains encrypted <b>master password</b>, used to encrypt other passwords</li>
<li>or it can contain a <b>relocation</b> - reference to another file, possibly on removable storage</li>
<li>this password is created first via CLI for now</li></ul></li>
-<li>server entries in the <tt>settings.xml</tt> have passwords and/or keystore passphrases encrypted
+<li>server entries in the <code>settings.xml</code> have passwords and/or keystore passphrases encrypted
<ul>
-<li>for now - this is done via CLI <b>after</b> master password has been created and stored in appropriate location</li></ul></li></ul></div>
-<div class="section">
+<li>for now - this is done via CLI <b>after</b> master password has been created and stored in appropriate location</li></ul></li></ul></section><section>
<h3><a name="How_to_create_a_master_password">How to create a master password</a></h3>
<p>Use the following command line:</p>
<div class="source"><pre class="prettyprint linenums">mvn --encrypt-master-password <password></pre></div>
<p><i>Note:</i> Since Maven 3.2.1 the password argument should no longer be used (see <a href="#Tips">Tips</a> below for more information). Maven will prompt for the password. Earlier versions of Maven will not prompt for a password, so it must be typed on the command-line in plaintext.</p>
<p>This command will produce an encrypted version of the password, something like</p>
<div class="source"><pre class="prettyprint linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</pre></div>
-<p>Store this password in the <tt>${user.home}/.m2/settings-security.xml</tt>; it should look like</p>
+<p>Store this password in the <code>${user.home}/.m2/settings-security.xml</code>; it should look like</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity></pre></div>
-<p>When this is done, you can start encrypting existing server passwords.</p></div>
-<div class="section">
+<p>When this is done, you can start encrypting existing server passwords.</p></section><section>
<h3><a name="How_to_encrypt_server_passwords">How to encrypt server passwords</a></h3>
<p>You will have to use the following command line:</p>
<div class="source"><pre class="prettyprint linenums">mvn --encrypt-password <password></pre></div>
-<p><i>Note:</i>Just like <tt>--encrypt-master-password</tt> the password argument should no longer be used since Maven 3.2.1 (see <a href="#Tips">Tips below for more information.</a>).</p>
+<p><i>Note:</i>Just like <code>--encrypt-master-password</code> the password argument should no longer be used since Maven 3.2.1 (see <a href="#Tips">Tips below for more information.</a>).</p>
<p>This command will produce an encrypted version of it, something like</p>
<div class="source"><pre class="prettyprint linenums">{COQLCE6DU6GtcS5P=}</pre></div>
-<p>Cut-n-paste it into your <tt>settings.xml</tt> file in the server section. This will look like:</p>
+<p>Cut-n-paste it into your <code>settings.xml</code> file in the server section. This will look like:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
<servers>
@@ -238,48 +235,42 @@ Robert Scholte" />
<p>Then you can use, say, deploy plugin, to write to this server:</p>
<div class="source"><pre class="prettyprint linenums">mvn deploy:deploy-file -Durl=https://maven.corp.com/repo \
-DrepositoryId=my.server \
- -Dfile=your-artifact-1.0.jar \</pre></div></div>
-<div class="section">
+ -Dfile=your-artifact-1.0.jar \</pre></div></section><section>
<h3><a name="How_to_keep_the_master_password_on_removable_drive">How to keep the master password on removable drive</a></h3>
-<p>Create the master password exactly as described above, and store it on a removable drive, for instance on OSX, my USB drive mounts as <tt>/Volumes/mySecureUsb</tt>, so I store</p>
+<p>Create the master password exactly as described above, and store it on a removable drive, for instance on OSX, my USB drive mounts as <code>/Volumes/mySecureUsb</code>, so I store</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity></pre></div>
-<p>in the file <tt>/Volumes/mySecureUsb/secure/settings-security.xml</tt></p>
-<p>And then I create <tt>${user.home}/.m2/settings-security.xml</tt> with the following content:</p>
+<p>in the file <code>/Volumes/mySecureUsb/secure/settings-security.xml</code></p>
+<p>And then I create <code>${user.home}/.m2/settings-security.xml</code> with the following content:</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<relocation>/Volumes/mySecureUsb/secure/settings-security.xml</relocation>
</settingsSecurity></pre></div>
-<p>This assures that encryption will only work when the usb drive is mounted by OS. This addresses a use case where only certain people are authorized to deploy and are issued these devices.</p></div>
-<div class="section">
-<h3><a name="Tips">Tips</a></h3>
-<div class="section">
+<p>This assures that encryption will only work when the usb drive is mounted by OS. This addresses a use case where only certain people are authorized to deploy and are issued these devices.</p></section><section>
+<h3><a name="Tips">Tips</a></h3><section>
<h4><a name="Escaping_curly-brace_literals_in_your_password_.28Since:_Maven_2.2.0.29"></a>Escaping curly-brace literals in your password <i>(Since: Maven 2.2.0)</i></h4>
<p>At times, you might find that your password (or the encrypted form of it) may actually contain '{' or '}' as a literal value. If you added such a password as-is to your settings.xml file, you would find that Maven does strange things with it. Specifically, Maven will treat all the characters preceding the '{' literal, and all the characters after the '}' literal, as comments. Obviously, this is not the behavior you want in such a situation. What you really need is a way of <b>escaping</b> the curly-brace literals in your password.</p>
<p>Starting in Maven 2.2.0, you can do just this, with the widely used '\' escape character. If your password looks like this:</p>
<div class="source"><pre class="prettyprint linenums">jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+{EF1iFQyJQ=</pre></div>
<p>Then, the value you would add to your settings.xml would look like this:</p>
-<div class="source"><pre class="prettyprint linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}</pre></div></div>
-<div class="section">
+<div class="source"><pre class="prettyprint linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+\{EF1iFQyJQ=}</pre></div></section><section>
<h4><a name="Password_Security"></a>Password Security</h4>
-<p>Editing <tt>settings.xml</tt> and running the above commands can still leave your password stored locally in plaintext. You may want to check the following locations:</p>
+<p>Editing <code>settings.xml</code> and running the above commands can still leave your password stored locally in plaintext. You may want to check the following locations:</p>
<ul>
-<li>Shell history (e.g. by running <tt>history</tt>). You may want to clear your history after encrypting the above passwords</li>
-<li>Editor caches (e.g. <tt>~/.viminfo</tt>)</li></ul>
-<p>Also note that the encrypted passwords can be decrypted by someone that has the master password and settings security file. Keep this file secure (or stored separately) if you expect the possibility that the <tt>settings.xml</tt> file may be retrieved.</p></div>
-<div class="section">
+<li>Shell history (e.g. by running <code>history</code>). You may want to clear your history after encrypting the above passwords</li>
+<li>Editor caches (e.g. <code>~/.viminfo</code>)</li></ul>
+<p>Also note that the encrypted passwords can be decrypted by someone that has the master password and settings security file. Keep this file secure (or stored separately) if you expect the possibility that the <code>settings.xml</code> file may be retrieved.</p></section><section>
<h4><a name="Password_Escaping_on_different_platforms"></a>Password Escaping on different platforms</h4>
-<p>On some platforms it might be neccessary to quote your password based on the content of your password in particular having special characters like <tt>%</tt>, <tt>!</tt>, <tt>$</tt> etc. in there. For example on Windows you have to be carefull about things like the following:</p>
+<p>On some platforms it might be neccessary to quote your password based on the content of your password in particular having special characters like <code>%</code>, <code>!</code>, <code>$</code> etc. in there. For example on Windows you have to be carefull about things like the following:</p>
<p>The following example will not work on Windows:</p>
<div class="source"><pre class="prettyprint linenums">mvn --encrypt-master-password a!$%^b</pre></div>
<p>whereas the following will work on Windows:</p>
<div class="source"><pre class="prettyprint linenums">mvn --encrypt-master-password "a!$%^b"</pre></div>
-<p>If you are on a linux/unix platform you should use single quotes for the above master password otherwise you will be astonished that the usage of the master-password will not work (caused by the dollar sign and furthermore the exclamation mark).</p></div>
-<div class="section">
+<p>If you are on a linux/unix platform you should use single quotes for the above master password otherwise you will be astonished that the usage of the master-password will not work (caused by the dollar sign and furthermore the exclamation mark).</p></section><section>
<h4><a name="Prompting_for_Password"></a>Prompting for Password</h4>
<p>In Maven before version 3.2.1 you have to give the password on command line as argument which means you might need to escape your password. In addition usually the shell stores the full history of commands you have entered, therefore anyone with access to your computer could restore the password from the shell`s history.</p>
<p>Starting with Maven 3.2.1 the password is an optional argument which means if you omit the password you will be prompted for it which prevents all the issues mentioned above.</p>
-<p>Therefore we strongly recommend to use Maven 3.2.1 and above to prevent problems with escaping special characters and of course security issues related to bash history or environment issues in relationship with the password.</p></div></div></div>
+<p>Therefore we strongly recommend to use Maven 3.2.1 and above to prevent problems with escaping special characters and of course security issues related to bash history or environment issues in relationship with the password.</p></section></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-generating-sources.html
==============================================================================
--- maven/website/content/guides/mini/guide-generating-sources.html (original)
+++ maven/website/content/guides/mini/guide-generating-sources.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-generating-sources.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-generating-sources.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -161,9 +161,9 @@ Karl Heinz Marbaise" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_generating_sources"></a>Guide to generating sources</h2>
-<p>Let's run though a short example to try and help. To generate sources you must first have a plugin that participates in the <tt>generate-sources</tt> phase like the <a class="externalLink" href="http://www.antlr.org/api/maven-plugin/latest/">ANTLR4 Maven Plugin</a>.</p>
+<p>Let's run though a short example to try and help. To generate sources you must first have a plugin that participates in the <code>generate-sources</code> phase like the <a class="externalLink" href="http://www.antlr.org/api/maven-plugin/latest/">ANTLR4 Maven Plugin</a>.</p>
<p>So this is all fine and dandy, we have a plugin that wants to generate some sources from a Antlr4 grammar but how do we use it. You need to specify that you want to use it in your POM:</p>
<div class="source"><pre class="prettyprint linenums">
<project>
@@ -188,7 +188,7 @@ Karl Heinz Marbaise" />
...
</project>
</pre></div>
-<p>If you then type <tt>mvn compile</tt> Maven will walk through the <a href="../introduction/introduction-to-the-lifecycle.html">lifecycle</a> and will eventually hit the <tt>generate-sources</tt> phase and see you have a plugin configured that wants to participate in that phase and the ANTLR4 Maven Plugin is executed with your given configuration. Furthermore during the compile you can observe that all the generated code (from your grammar files) will automatically being compiled without supplemental configuration.</p></div>
+<p>If you then type <code>mvn compile</code> Maven will walk through the <a href="../introduction/introduction-to-the-lifecycle.html">lifecycle</a> and will eventually hit the <code>generate-sources</code> phase and see you have a plugin configured that wants to participate in that phase and the ANTLR4 Maven Plugin is executed with your given configuration. Furthermore during the compile you can observe that all the generated code (from your grammar files) will automatically being compiled without supplemental configuration.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-http-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-http-settings.html (original)
+++ maven/website/content/guides/mini/guide-http-settings.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-http-settings.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-http-settings.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,7 +160,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Advanced_Configuration_of_the_HttpClient_HTTP_Wagon"></a>Advanced Configuration of the HttpClient HTTP Wagon</h2>
<ul>
<li><a href="#Advanced_Configuration_of_the_HttpClient_HTTP_Wagon">Advanced Configuration of the HttpClient HTTP Wagon</a>
@@ -184,28 +184,22 @@
<li><a href="#HTTP_Headers">HTTP Headers</a></li>
<li><a href="#Connection_Timeouts">Connection Timeouts</a></li>
<li><a href="#Read_time_out">Read time out</a></li></ul></li>
-<li><a href="#Resources">Resources</a></li></ul></li></ul>
-<div class="section">
-<h3><a name="Notice_on_Maven_Versioning_and_Availability"></a>Notice on Maven Versioning and Availability</h3>
-<div class="section">
+<li><a href="#Resources">Resources</a></li></ul></li></ul><section>
+<h3><a name="Notice_on_Maven_Versioning_and_Availability"></a>Notice on Maven Versioning and Availability</h3><section>
<h4><a name="Maven_2.2.0"></a>Maven 2.2.0</h4>
-<p>Starting in <b>Maven 2.2.0</b>, the HttpClient wagon was the implementation in use. The remainder of this document deals specifically with the differences between the HttpClient- and Sun-based HTTP wagons.</p></div>
-<div class="section">
+<p>Starting in <b>Maven 2.2.0</b>, the HttpClient wagon was the implementation in use. The remainder of this document deals specifically with the differences between the HttpClient- and Sun-based HTTP wagons.</p></section><section>
<h4><a name="Maven_2.2.1"></a>Maven 2.2.1</h4>
<p>Due to several critical issues introduced by the HttpClient-based HTTP wagon, <b>Maven 2.2.1</b> reverted back to the Sun implementation (a.k.a. 'lightweight') of the HTTP wagon as the default for HTTP/HTTPS transfers. The issues with the HttpClient-based wagon were mainly related to checksums, transfer timeouts, and NTLM proxies, and served as the primary cause for the release of <b>2.2.1</b> in the first place.</p>
-<p><b>However</b>, starting in <b>Maven 2.2.1</b> you have a choice: you can use the default wagon implementation for a given protocol, or you can select an alternative wagon <tt>provider</tt> you'd like to use on a per-protocol basis. For more information, see the <a href="./guide-wagon-providers.html">Guide to Wagon Providers</a> [3].</p></div>
-<div class="section">
+<p><b>However</b>, starting in <b>Maven 2.2.1</b> you have a choice: you can use the default wagon implementation for a given protocol, or you can select an alternative wagon <code>provider</code> you'd like to use on a per-protocol basis. For more information, see the <a href="./guide-wagon-providers.html">Guide to Wagon Providers</a> [3].</p></section><section>
<h4><a name="Maven_3.0.4"></a>Maven 3.0.4</h4>
<p>With 3.0.4, the default wagon http(s) is now the HttpClient based on <a class="externalLink" href="http://hc.apache.org/httpcomponents-client-ga">Apache Http Client 4.1.2</a>. There is now a http connection pooling to prevent reopening http(s) to remote server for each requests. This pool feature is configurable with some parameters [4].</p>
<p>This new defaut wagon comes with some default configuration:</p>
<ul>
<li>http(s) connection pool: default to 20.</li>
-<li>readTimeout: default to 1800000ms (~30 minutes) (see section <tt>Read time out</tt> below)</li>
-<li>default Preemptive Authentication only with PUT (GET doesn't use anymore default Preemptive Authentication)</li></ul></div></div>
-<div class="section">
+<li>readTimeout: default to 1800000ms (~30 minutes) (see section <code>Read time out</code> below)</li>
+<li>default Preemptive Authentication only with PUT (GET doesn't use anymore default Preemptive Authentication)</li></ul></section></section><section>
<h3><a name="Introduction"></a>Introduction</h3>
-<p>Using the HttpClient-based HTTP wagon, you have a lot more control over the configuration used to access HTTP-based Maven repositories. For starters, you have fine-grained control over what HTTP headers are used when resolving artifacts. In addition, you can also configure a wide range of parameters to control the behavior of HttpClient itself. Best of all, you have the ability to control these headers and parameters for all requests, or individual request types (Maven issues GET, HEAD, and PUT requests for different parts of the artifact-management subsystem).</p></div>
-<div class="section">
+<p>Using the HttpClient-based HTTP wagon, you have a lot more control over the configuration used to access HTTP-based Maven repositories. For starters, you have fine-grained control over what HTTP headers are used when resolving artifacts. In addition, you can also configure a wide range of parameters to control the behavior of HttpClient itself. Best of all, you have the ability to control these headers and parameters for all requests, or individual request types (Maven issues GET, HEAD, and PUT requests for different parts of the artifact-management subsystem).</p></section><section>
<h3><a name="The_Basics"></a>The Basics</h3>
<p>Without any special configuration, Maven's HTTP wagon will use some default HTTP headers and client parameters when managing artifacts. The default headers are:</p>
<div class="source"><pre class="prettyprint linenums">Cache-control: no-cache
@@ -230,11 +224,10 @@ the target server's authentication.
'Expect: 100-continue' handshake should be used with caution, as it may cause
problems with HTTP servers and proxies that do not support HTTP/1.1 protocol.</pre></div>
<p>Without this setting, PUT requests that require authentication will transfer their entire payload to the server before that server issues an authentication challenge. In order to complete the PUT request, the client must then re-send the payload with the proper credentials specified in the HTTP headers. This results in twice the bandwidth usage, and twice the time to transfer each artifact.</p>
-<p>Another option to avoid this double transfer is what's known as preemptive authentication, which involves sending the authentication headers along with the original PUT request. However, there are a few potential issues with this approach. For one thing, in the event you have an unused <tt><server></tt> entry that specifies an invalid username/password combination, some servers may respond with a <tt>401 Unauthorized</tt> even if the server doesn't actually require any authentication for the request. In addition, blindly sending authentication credentials with every request regardless of whether the server has made a challenge can result in a security hole, since the server may not make provisions to secure credentials for paths that don't require authentication.</p>
-<p>We'll discuss preemptive authentication in another example, below.</p></div>
-<div class="section">
+<p>Another option to avoid this double transfer is what's known as preemptive authentication, which involves sending the authentication headers along with the original PUT request. However, there are a few potential issues with this approach. For one thing, in the event you have an unused <code><server></code> entry that specifies an invalid username/password combination, some servers may respond with a <code>401 Unauthorized</code> even if the server doesn't actually require any authentication for the request. In addition, blindly sending authentication credentials with every request regardless of whether the server has made a challenge can result in a security hole, since the server may not make provisions to secure credentials for paths that don't require authentication.</p>
+<p>We'll discuss preemptive authentication in another example, below.</p></section><section>
<h3><a name="Configuring_GET.2C_HEAD.2C_PUT.2C_or_All_of_the_Above"></a>Configuring GET, HEAD, PUT, or All of the Above</h3>
-<p>In all of the examples below, it's important to understand that we can configure the HTTP settings for all requests made to a given server, or for only one method. To configure all methods for a server, you'd use the following section of the <tt>settings.xml</tt> file:</p>
+<p>In all of the examples below, it's important to understand that we can configure the HTTP settings for all requests made to a given server, or for only one method. To configure all methods for a server, you'd use the following section of the <code>settings.xml</code> file:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
[...]
<servers>
@@ -266,10 +259,9 @@ problems with HTTP servers and proxies t
</server>
</servers>
</settings></pre></div>
-<p>For clarity, the other two sections are <tt><get></tt> for GET requests, and <tt><head></tt> for HEAD requests. I know that's going to be hard to remember...</p></div>
-<div class="section">
+<p>For clarity, the other two sections are <code><get></code> for GET requests, and <code><head></code> for HEAD requests. I know that's going to be hard to remember...</p></section><section>
<h3><a name="Taking_Control_of_Your_HTTP_Headers"></a>Taking Control of Your HTTP Headers</h3>
-<p>As you may have noticed above, the default HTTP headers do have the potential to cause problems. For instance, some websites set the encoding for downloading GZipped files as <tt>gzip</tt>, in spite of the fact that the HTTP request itself isn't being sent using GZip compression. If the client is using the <tt>Accept-Encoding: gzip</tt> header, this can result in the client itself decompressing the GZipped file <i>during the transfer</i> and writing the decompressed file to the local disk with the original filename. This can be misleading to say the least, and can use up an inordinate amount of disk space on the local computer.</p>
+<p>As you may have noticed above, the default HTTP headers do have the potential to cause problems. For instance, some websites set the encoding for downloading GZipped files as <code>gzip</code>, in spite of the fact that the HTTP request itself isn't being sent using GZip compression. If the client is using the <code>Accept-Encoding: gzip</code> header, this can result in the client itself decompressing the GZipped file <i>during the transfer</i> and writing the decompressed file to the local disk with the original filename. This can be misleading to say the least, and can use up an inordinate amount of disk space on the local computer.</p>
<p>To turn off this default behavior, we'll simply disable the default headers. Then, we'll need to respecify the other headers that we are still interested in, like this:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
[...]
@@ -309,28 +301,25 @@ problems with HTTP servers and proxies t
[...]
</servers>
[...]
-</settings></pre></div></div>
-<div class="section">
+</settings></pre></div></section><section>
<h3><a name="Fine-Tuning_HttpClient_Parameters"></a>Fine-Tuning HttpClient Parameters</h3>
-<p>Going beyond the power of HTTP request parameters, HttpClient provides a host of other configuration options. In most cases, you won't need to customize these. But in case you do, Maven provides access to specify your own fine-grained configuration for HttpClient. Again, you can specify these parameter customizations per-method (HEAD, GET, or PUT), or for all methods of interacting with a given server. For a complete list of supported parameters, see the link[2] in Resources section below.</p>
-<div class="section">
+<p>Going beyond the power of HTTP request parameters, HttpClient provides a host of other configuration options. In most cases, you won't need to customize these. But in case you do, Maven provides access to specify your own fine-grained configuration for HttpClient. Again, you can specify these parameter customizations per-method (HEAD, GET, or PUT), or for all methods of interacting with a given server. For a complete list of supported parameters, see the link[2] in Resources section below.</p><section>
<h4><a name="Non-String_Parameter_Values"></a>Non-String Parameter Values</h4>
<p>Many of the configuration parameters for HttpClient have simple string values; however, there are important exceptions to this. In some cases, you may need to specify boolean, integer, or long values. In others, you may even need to specify a collection of string values. You can specify these using a simple formatting syntax, as follows:</p>
<ol style="list-style-type: decimal">
-<li><b>booleans:</b> <tt>%b,<value></tt></li>
-<li><b>integer:</b> <tt>%i,<value></tt></li>
-<li><b>long:</b> <tt>%l,<value></tt> (yes, that's an 'L', not a '1')</li>
-<li><b>double:</b> <tt>%d,<value></tt></li>
-<li><b>collection of strings:</b> <tt>%c,<value1>,<value2>,<value3>,...</tt>, which could also be specified as:
+<li><b>booleans:</b> <code>%b,<value></code></li>
+<li><b>integer:</b> <code>%i,<value></code></li>
+<li><b>long:</b> <code>%l,<value></code> (yes, that's an 'L', not a '1')</li>
+<li><b>double:</b> <code>%d,<value></code></li>
+<li><b>collection of strings:</b> <code>%c,<value1>,<value2>,<value3>,...</code>, which could also be specified as:
<div class="source"><pre class="prettyprint linenums">%c,
<value1>,
<value2>,
<value3>,
...</pre></div></li></ol>
-<p>As you may have noticed, this syntax is similar to the format-and-data strategy used by functions like <tt>sprintf()</tt> in many languages. The syntax has been chosen with this similarity in mind, to make it a little more intuitive to use.</p></div>
-<div class="section">
+<p>As you may have noticed, this syntax is similar to the format-and-data strategy used by functions like <code>sprintf()</code> in many languages. The syntax has been chosen with this similarity in mind, to make it a little more intuitive to use.</p></section><section>
<h4><a name="Example:_Using_Preemptive_Authentication"></a>Example: Using Preemptive Authentication</h4>
-<p>Using the above syntax, we can configure preemptive authentication for PUT requests using the boolean HttpClient parameter <tt>http.authentication.preemptive</tt>, like this:</p>
+<p>Using the above syntax, we can configure preemptive authentication for PUT requests using the boolean HttpClient parameter <code>http.authentication.preemptive</code>, like this:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
<servers>
<server>
@@ -364,10 +353,9 @@ problems with HTTP servers and proxies t
</configuration>
</server>
</servers>
-</settings></pre></div></div>
-<div class="section">
+</settings></pre></div></section><section>
<h4><a name="Ignoring_Cookies"></a>Ignoring Cookies</h4>
-<p>Like the example above, telling the HttpClient to ignore cookies for all methods of request is a simple matter of configuring the <tt>http.protocol.cookie-policy</tt> parameter (it uses a regular string value, so no special syntax is required):</p>
+<p>Like the example above, telling the HttpClient to ignore cookies for all methods of request is a simple matter of configuring the <code>http.protocol.cookie-policy</code> parameter (it uses a regular string value, so no special syntax is required):</p>
<div class="source"><pre class="prettyprint linenums"><settings>
<servers>
<server>
@@ -387,11 +375,9 @@ problems with HTTP servers and proxies t
</server>
</servers>
</settings></pre></div>
-<p>The configuration above can be useful in cases where the repository is using cookies - like the session cookies that are often mistakenly turned on or left on in appservers - alongside HTTP redirection. In these cases, it becomes far more likely that the cookie issued by the appserver will use a <tt>Path</tt> that is inconsistent with the one used by the client to access the server. If you have this problem, and know that you don't need to use this session cookie, you can ignore cookies from this server with the above configuration.</p></div></div>
-<div class="section">
+<p>The configuration above can be useful in cases where the repository is using cookies - like the session cookies that are often mistakenly turned on or left on in appservers - alongside HTTP redirection. In these cases, it becomes far more likely that the cookie issued by the appserver will use a <code>Path</code> that is inconsistent with the one used by the client to access the server. If you have this problem, and know that you don't need to use this session cookie, you can ignore cookies from this server with the above configuration.</p></section></section><section>
<h3><a name="Support_for_General-Wagon_Configuration_Standards"></a>Support for General-Wagon Configuration Standards</h3>
-<p>It should be noted that configuration options previously available in the HttpClient-driven HTTP wagon are still supported in addition to this new, fine-grained approach. These include the configuration of HTTP headers and connection timeouts. Let's examine each of these briefly:</p>
-<div class="section">
+<p>It should be noted that configuration options previously available in the HttpClient-driven HTTP wagon are still supported in addition to this new, fine-grained approach. These include the configuration of HTTP headers and connection timeouts. Let's examine each of these briefly:</p><section>
<h4><a name="HTTP_Headers"></a>HTTP Headers</h4>
<p>In all HTTP Wagon implementations, you can add your own HTTP headers like this:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
@@ -409,10 +395,9 @@ problems with HTTP servers and proxies t
</server>
</servers>
</settings></pre></div>
-<p>It's important to understand that the above approach doesn't allow you to turn off all of the default HTTP headers; nor does it allow you to specify headers on a per-method basis. However, this configuration remains available in both the lightweight and httpclient-based Wagon implementations.</p></div>
-<div class="section">
+<p>It's important to understand that the above approach doesn't allow you to turn off all of the default HTTP headers; nor does it allow you to specify headers on a per-method basis. However, this configuration remains available in both the lightweight and httpclient-based Wagon implementations.</p></section><section>
<h4><a name="Connection_Timeouts"></a>Connection Timeouts</h4>
-<p>All wagon implementations that extend the <tt>AbstractWagon</tt> class, including those for SCP, HTTP, FTP, and more, allow the configuration of a connection timeout, to allow the user to tell Maven how long to wait before giving up on a connection that has not responded. This option is preserved in the HttpClient-based wagon, but this wagon also provides a fine-grained alternative configuration that can allow you to specify timeouts per-method for a given server. The old configuration option - which is still supported - looks like this:</p>
+<p>All wagon implementations that extend the <code>AbstractWagon</code> class, including those for SCP, HTTP, FTP, and more, allow the configuration of a connection timeout, to allow the user to tell Maven how long to wait before giving up on a connection that has not responded. This option is preserved in the HttpClient-based wagon, but this wagon also provides a fine-grained alternative configuration that can allow you to specify timeouts per-method for a given server. The old configuration option - which is still supported - looks like this:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
<servers>
<server>
@@ -438,8 +423,7 @@ problems with HTTP servers and proxies t
</server>
</servers>
</settings></pre></div>
-<p>If all you need is a per-server timeout configuration, you still have the option to use the old <tt><timeout></tt> parameter. If you need to separate timeout preferences according to HTTP method, you can use one more like that specified directly above.</p></div>
-<div class="section">
+<p>If all you need is a per-server timeout configuration, you still have the option to use the old <code><timeout></code> parameter. If you need to separate timeout preferences according to HTTP method, you can use one more like that specified directly above.</p></section><section>
<h4><a name="Read_time_out"></a>Read time out</h4>
<p>With Wagon 2.0 and Apache Maven 3.0.4, a default timeout of 30 minutes comes by default. If you want to change this value, you can add the following setup in your settings:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
@@ -455,14 +439,13 @@ problems with HTTP servers and proxies t
</configuration>
</server>
</servers>
-</settings></pre></div></div></div>
-<div class="section">
+</settings></pre></div></section></section><section>
<h3><a name="Resources"></a>Resources</h3>
<ol style="list-style-type: decimal">
<li><a class="externalLink" href="http://hc.apache.org/httpclient-3.x/">HttpClient website</a></li>
<li><a class="externalLink" href="http://hc.apache.org/httpclient-3.x/preference-api.html">HttpClient preference architecture and configuration guide</a></li>
<li><a href="./guide-wagon-providers.html">Guide to Wagon Providers</a></li>
-<li><a href="/wagon/wagon-providers/wagon-http/">Wagon Http</a></li></ol></div></div>
+<li><a href="/wagon/wagon-providers/wagon-http/">Wagon Http</a></li></ol></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-manifest.html
==============================================================================
--- maven/website/content/guides/mini/guide-manifest.html (original)
+++ maven/website/content/guides/mini/guide-manifest.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-manifest.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-manifest.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -161,9 +161,9 @@ Dennis Lundberg" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_Working_with_Manifests"></a>Guide to Working with Manifests</h2>
-<p>In order to modify the manifest of the archive produced by the packaging plug-ins you need to create a configuration for it. The definitive guide for this is <a href="/shared/maven-archiver/index.html">the site for the Maven Archiver shared component</a>. This component is used by all our packaging plugins.</p></div>
+<p>In order to modify the manifest of the archive produced by the packaging plug-ins you need to create a configuration for it. The definitive guide for this is <a href="/shared/maven-archiver/index.html">the site for the Maven Archiver shared component</a>. This component is used by all our packaging plugins.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-maven-classloading.html
==============================================================================
--- maven/website/content/guides/mini/guide-maven-classloading.html (original)
+++ maven/website/content/guides/mini/guide-maven-classloading.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-maven-classloading.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-maven-classloading.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -161,32 +161,28 @@ Anders Kristian Andersen" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_Maven_Classloading"></a>Guide to Maven Classloading</h2>
-<p>This is a description of the classloader hierarchy in Maven 2.0.6+.</p>
-<div class="section">
+<p>This is a description of the classloader hierarchy in Maven 2.0.6+.</p><section>
<h3><a name="Overview"></a>Overview</h3>
<ul>
<li>System Classloader</li>
<li>Core Classloader</li>
<li>Plugin Classloaders</li>
-<li>Custom Classloaders</li></ul></div>
-<div class="section">
+<li>Custom Classloaders</li></ul></section><section>
<h3><a name="a1._System_Classloader"></a>1. <a name="System_Classloader">System Classloader</a></h3>
-<p>Maven uses the <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-classworlds/">Plexus Classworlds</a> classloading framework with which we create our classloader graph. If you look in your <tt>${maven.home}/boot</tt> directory you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java <tt>CLASSPATH</tt> and Classworlds then builds the other classloaders or realms in Classworlds terminology.</p>
+<p>Maven uses the <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-classworlds/">Plexus Classworlds</a> classloading framework with which we create our classloader graph. If you look in your <code>${maven.home}/boot</code> directory you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java <code>CLASSPATH</code> and Classworlds then builds the other classloaders or realms in Classworlds terminology.</p>
<p>An Ant script like this will show the contents of the system classloader:</p>
<div>
<pre> <target name="info">
<echo>java.class.path=${java.class.path}</echo>
- </target></pre></div></div>
-<div class="section">
+ </target></pre></div></section><section>
<h3><a name="a2._Core_Classloader"></a>2. <a name="Core_Classloader">Core Classloader</a></h3>
-<p>The second classloader down the graph contains the core requirements of Maven. More precisely, the core classloader has the libraries in <tt>${maven.home}/lib</tt>. In general these are just Maven libraries, e.g. instances of <tt><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> belong to this classloader. We hope to further separate these in the future to just be Maven APIs and have the implementations selected at runtime as required by the system.</p>
-<p>You can add elements to this classloader by <a href="/ref/current/maven-model/maven.html#class_extension">extensions</a>. These are loaded into the same place as <tt>${maven.home}/lib</tt> and hence are available to the Maven core and all plugins for the current project and subsequent projects (in future, we plan to remove it from subsequent projects).</p></div>
-<div class="section">
+<p>The second classloader down the graph contains the core requirements of Maven. More precisely, the core classloader has the libraries in <code>${maven.home}/lib</code>. In general these are just Maven libraries, e.g. instances of <code><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></code> belong to this classloader. We hope to further separate these in the future to just be Maven APIs and have the implementations selected at runtime as required by the system.</p>
+<p>You can add elements to this classloader by <a href="/ref/current/maven-model/maven.html#class_extension">extensions</a>. These are loaded into the same place as <code>${maven.home}/lib</code> and hence are available to the Maven core and all plugins for the current project and subsequent projects (in future, we plan to remove it from subsequent projects).</p></section><section>
<h3><a name="a3._Plugin_Classloaders"></a>3. <a name="Plugin_Classloaders">Plugin Classloaders</a></h3>
<p>After that, each plugin has its own classloader that is a child of Maven's core classloader. The classes in this classloader are taken from the dependencies in the plugin's dependency list.</p>
-<p>Users can add dependencies to this classloader by adding dependencies to a plugin in the <tt><a href="/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></tt> section of their project <tt>pom.xml</tt>. Here is a sample of adding <tt>ant-nodeps</tt> to the plugin classloader of the Antrun Plugin and hereby enabling the use of additional/optional Ant tasks:</p>
+<p>Users can add dependencies to this classloader by adding dependencies to a plugin in the <code><a href="/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></code> section of their project <code>pom.xml</code>. Here is a sample of adding <code>ant-nodeps</code> to the plugin classloader of the Antrun Plugin and hereby enabling the use of additional/optional Ant tasks:</p>
<div>
<pre> <plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -201,13 +197,12 @@ Anders Kristian Andersen" />
</dependencies>
...
</plugin></pre></div>
-<p>Plugins can inspect their effective runtime class path via the expressions <tt>${plugin.artifacts}</tt> or <tt>${plugin.artifactMap}</tt> to have a list or map, respectively, of resolved artifacts injected from the <tt><a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html">PluginDescriptor</a></tt>.</p>
-<p>Please note that the plugin classloader does neither contain the <a href="/ref/current/maven-model/maven.html#class_dependency">dependencies</a> of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the <tt><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> in combination with the mojo annotation <tt>requiresDependencyResolution</tt> from the <a href="/developers/mojo-api-specification.html">Mojo API Specification</a>. For instance, flagging a mojo with <tt>@requiresDependencyResolution runtime</tt> enables it to query the runtime class path of the current project from which it could create further classloaders.</p>
-<p>When a build plugin is executed, the thread's context classloader is set to the plugin classloader.</p></div>
-<div class="section">
+<p>Plugins can inspect their effective runtime class path via the expressions <code>${plugin.artifacts}</code> or <code>${plugin.artifactMap}</code> to have a list or map, respectively, of resolved artifacts injected from the <code><a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html">PluginDescriptor</a></code>.</p>
+<p>Please note that the plugin classloader does neither contain the <a href="/ref/current/maven-model/maven.html#class_dependency">dependencies</a> of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the <code><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></code> in combination with the mojo annotation <code>requiresDependencyResolution</code> from the <a href="/developers/mojo-api-specification.html">Mojo API Specification</a>. For instance, flagging a mojo with <code>@requiresDependencyResolution runtime</code> enables it to query the runtime class path of the current project from which it could create further classloaders.</p>
+<p>When a build plugin is executed, the thread's context classloader is set to the plugin classloader.</p></section><section>
<h3><a name="a4._Custom_Classloaders"></a>4. <a name="Custom_Classloaders">Custom Classloaders</a></h3>
<p>Plugins are free to create further classloaders on their discretion. For example, a plugin might want to create a classloader that combines the plugin class path and the project class path.</p>
-<p>It is important to understand that the plugin classloader cannot load classes from any of those custom classloaders. Some factory patterns require that. Here you must add the classes to the plugin classloader as shown before.</p></div></div>
+<p>It is important to understand that the plugin classloader cannot load classes from any of those custom classloaders. Some factory patterns require that. Here you must add the classes to the plugin classloader as shown before.</p></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-mirror-settings.html
==============================================================================
--- maven/website/content/guides/mini/guide-mirror-settings.html (original)
+++ maven/website/content/guides/mini/guide-mirror-settings.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-mirror-settings.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-mirror-settings.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -162,7 +162,7 @@ Robert Scholte" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Using_Mirrors_for_Repositories"></a>Using Mirrors for Repositories</h2>
<p>With <a href="/guides/introduction/introduction-to-repositories.html">Repositories</a> you specify from which locations you want to <i>download</i> certain artifacts, such as dependencies and maven-plugins. Repositories can be declared inside a project, which means that if you have your own custom repositories, those sharing your project easily get the right settings out of the box. However, you may want to use an alternative mirror for a particular repository without changing the project files.</p>
<p>Some reasons to use a mirror are:</p>
@@ -170,7 +170,7 @@ Robert Scholte" />
<li>There is a synchronized mirror on the internet that is geographically closer and faster</li>
<li>You want to replace a particular repository with your own internal repository which you have greater control over</li>
<li>You want to run a <a href="../../repository-management.html">repository manager</a> to provide a local cache to a mirror and need to use its URL instead</li></ul>
-<p>To configure a mirror of a given repository, you provide it in your settings file (<tt>${user.home}/.m2/settings.xml</tt>), giving the new repository its own <tt>id</tt> and <tt>url</tt>, and specify the <tt>mirrorOf</tt> setting that is the ID of the repository you are using a mirror of. For example, the ID of the main Maven Central US repository included by default is <tt>central</tt>, so to use the European Central instance, you would configure the following:</p>
+<p>To configure a mirror of a given repository, you provide it in your settings file (<code>${user.home}/.m2/settings.xml</code>), giving the new repository its own <code>id</code> and <code>url</code>, and specify the <code>mirrorOf</code> setting that is the ID of the repository you are using a mirror of. For example, the ID of the main Maven Central US repository included by default is <code>central</code>, so to use the European Central instance, you would configure the following:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
<mirrors>
@@ -183,14 +183,13 @@ Robert Scholte" />
</mirrors>
...
</settings></pre></div>
-<p>Note that there can be at most one mirror for a given repository. In other words, you cannot map a single repository to a group of mirrors that all define the same <tt><mirrorOf></tt> value. Maven will not aggregate the mirrors but simply picks the first match. If you want to provide a combined view of several repositories, use a <a href="../../repository-management.html">repository manager</a> instead.</p>
+<p>Note that there can be at most one mirror for a given repository. In other words, you cannot map a single repository to a group of mirrors that all define the same <code><mirrorOf></code> value. Maven will not aggregate the mirrors but simply picks the first match. If you want to provide a combined view of several repositories, use a <a href="../../repository-management.html">repository manager</a> instead.</p>
<p>The settings descriptor documentation can be found on the <a href="../../maven-settings/settings.html">Maven Local Settings Model Website</a>.</p>
-<p><b>Note</b>: The official Maven 2 repository is at <tt>http://repo.maven.apache.org/maven2</tt> hosted in the US, or <tt>http://uk.maven.org/maven2</tt> hosted in the UK. </p>
-<p>A list of known mirrors is available in the <a class="externalLink" href="http://repo.maven.apache.org/maven2/.meta/repository-metadata.xml">Repository Metadata</a>. These mirrors may not have the same contents and we don't support them in any way.</p></div>
-<div class="section">
+<p><b>Note</b>: The official Maven 2 repository is at <code>http://repo.maven.apache.org/maven2</code> hosted in the US, or <code>http://uk.maven.org/maven2</code> hosted in the UK. </p>
+<p>A list of known mirrors is available in the <a class="externalLink" href="http://repo.maven.apache.org/maven2/.meta/repository-metadata.xml">Repository Metadata</a>. These mirrors may not have the same contents and we don't support them in any way.</p></section><section>
<h2><a name="Using_A_Single_Repository"></a>Using A Single Repository</h2>
<p>You can force Maven to use a single repository by having it mirror all repository requests. The repository must contain all of the desired artifacts, or be able to proxy the requests to other repositories. This setting is most useful when using an internal company repository with a <a href="../../repository-management.html">Maven Repository Manager</a> to proxy external requests.</p>
-<p>To achieve this, set <tt>mirrorOf</tt> to <tt>*</tt>.</p>
+<p>To achieve this, set <code>mirrorOf</code> to <code>*</code>.</p>
<p><b>Note:</b> This feature is only available in Maven 2.0.5+.</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
@@ -203,24 +202,23 @@ Robert Scholte" />
</mirror>
</mirrors>
...
-</settings></pre></div></div>
-<div class="section">
+</settings></pre></div></section><section>
<h2><a name="Advanced_Mirror_Specification"></a>Advanced Mirror Specification</h2>
<p>A single mirror can handle multiple repositories when used in conjunction with a repository manager.</p>
<p>The syntax as of Maven 2.0.9:</p>
<ul>
-<li><tt>*</tt> matches all repo ids.</li>
-<li><tt>external:*</tt> matches all repositories except those using localhost or file based repositories. This is used in conjunction with a repository manager when you want to exclude redirecting repositories that are defined for Integration Testing.</li>
+<li><code>*</code> matches all repo ids.</li>
+<li><code>external:*</code> matches all repositories except those using localhost or file based repositories. This is used in conjunction with a repository manager when you want to exclude redirecting repositories that are defined for Integration Testing.</li>
<li>multiple repositories may be specified using a comma as the delimiter</li>
<li>an exclamation mark may be used in conjunction with one of the above wildcards to exclude a repository id</li></ul>
<p>The position of wildcards within a comma separated list of repository identifiers is not important as the wildcards defer to further processing and explicit includes or excludes stop the processing, overruling any wildcard match.</p>
-<p>When you use the advanced syntax and configure multiple mirrors, keep in mind that their declaration order matters. When Maven looks for a mirror of some repository, it first checks for a mirror whose <tt><mirrorOf></tt> exactly matches the repository identifier. If no direct match is found, Maven picks the first mirror declaration that matches according to the rules above (if any). Hence, you may influence match order by changing the order of the definitions in the <tt>settings.xml</tt></p>
+<p>When you use the advanced syntax and configure multiple mirrors, keep in mind that their declaration order matters. When Maven looks for a mirror of some repository, it first checks for a mirror whose <code><mirrorOf></code> exactly matches the repository identifier. If no direct match is found, Maven picks the first mirror declaration that matches according to the rules above (if any). Hence, you may influence match order by changing the order of the definitions in the <code>settings.xml</code></p>
<p>Examples:</p>
<ul>
-<li><tt>*</tt> = everything</li>
-<li><tt>external:*</tt> = everything not on the localhost and not file based.</li>
-<li><tt>repo,repo1</tt> = repo or repo1</li>
-<li><tt>*,!repo1</tt> = everything except repo1</li></ul>
+<li><code>*</code> = everything</li>
+<li><code>external:*</code> = everything not on the localhost and not file based.</li>
+<li><code>repo,repo1</code> = repo or repo1</li>
+<li><code>*,!repo1</code> = everything except repo1</li></ul>
<p><b>Note:</b> This feature is only available in Maven 2.0.9+.</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
@@ -239,11 +237,10 @@ Robert Scholte" />
</mirror>
</mirrors>
...
-</settings></pre></div></div>
-<div class="section">
+</settings></pre></div></section><section>
<h2><a name="Creating_Your_Own_Mirror"></a>Creating Your Own Mirror</h2>
<p>The size of the central repository is <a class="externalLink" href="http://search.maven.org/#stats">increasing steadily</a> To save us bandwidth and you time, mirroring the entire central repository is not allowed. (Doing so will get you automatically banned) Instead, we suggest you setup a <a href="../../repository-management.html">repository manager</a> as a proxy.</p>
-<p>If you really want to become an official mirror, contact us at <a class="externalLink" href="https://issues.sonatype.org/browse/MVNCENTRAL">MVNCENTRAL</a> with your location and we'll work to get you setup.</p></div>
+<p>If you really want to become an official mirror, contact us at <a class="externalLink" href="https://issues.sonatype.org/browse/MVNCENTRAL">MVNCENTRAL</a> with your location and we'll work to get you setup.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-multiple-modules.html
==============================================================================
--- maven/website/content/guides/mini/guide-multiple-modules.html (original)
+++ maven/website/content/guides/mini/guide-multiple-modules.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-multiple-modules.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-multiple-modules.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -161,17 +161,15 @@ Karl Heinz Marbaise" />
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_Working_with_Multiple_Modules"></a>Guide to Working with Multiple Modules</h2>
-<p>As seen in the introduction to the POM, Maven supports project aggregation in addition to project inheritance. This section outlines how Maven processes projects with multiple modules, and how you can work with them more effectively.</p>
-<div class="section">
+<p>As seen in the introduction to the POM, Maven supports project aggregation in addition to project inheritance. This section outlines how Maven processes projects with multiple modules, and how you can work with them more effectively.</p><section>
<h3><a name="The_Reactor"></a>The Reactor</h3>
<p>The mechanism in Maven that handles multi-module projects is referred to as the <i>reactor</i>. This part of the Maven core does the following:</p>
<ul>
<li>Collects all the available modules to build</li>
<li>Sorts the projects into the correct build order</li>
-<li>Builds the selected projects in order</li></ul>
-<div class="section">
+<li>Builds the selected projects in order</li></ul><section>
<h4><a name="Reactor_Sorting"></a>Reactor Sorting</h4>
<p>Because modules within a multi-module build can depend on each other, it is important that the reactor sorts all the projects in a way that guarantees any project is built before it is required.</p>
<p>The following relationships are honoured when sorting projects:</p>
@@ -180,24 +178,22 @@ Karl Heinz Marbaise" />
<li>a plugin declaration where the plugin is another module in the build</li>
<li>a plugin dependency on another module in the build</li>
<li>a build extension declaration on another module in the build</li>
-<li>the order declared in the <tt><modules></tt> element (if no other rule applies)</li></ul>
-<p>Note that only "instantiated" references are used - <tt>dependencyManagement</tt> and <tt>pluginManagement</tt> elements do not cause a change to the reactor sort order.</p></div>
-<div class="section">
+<li>the order declared in the <code><modules></code> element (if no other rule applies)</li></ul>
+<p>Note that only "instantiated" references are used - <code>dependencyManagement</code> and <code>pluginManagement</code> elements do not cause a change to the reactor sort order.</p></section><section>
<h4><a name="Command_Line_Options"></a>Command Line Options</h4>
<p>No special configuration is required to take advantage of the reactor, however it is possible to customize its behavior.</p>
<p>The following command line switches are available:</p>
<ul>
-<li><tt>--resume-from</tt> - resumes a reactor the specified project (e.g. when it fails in the middle)</li>
-<li><tt>--also-make</tt> - build the specified projects, and any of their dependencies in the reactor</li>
-<li><tt>--also-make-dependents</tt> - build the specified projects, and any that depend on them</li>
-<li><tt>--fail-fast</tt> - the default behavior - whenever a module build fails, stop the overall build immediately</li>
-<li><tt>--fail-at-end</tt> - if a particular module build fails, continue the rest of the reactor and report all failed modules at the end instead</li>
-<li><tt>--non-recursive</tt> - do not use a reactor build, even if the current project declares modules and just build the project in the current directory</li></ul>
-<p>Refer to the Maven command line interface reference for more information on these switches.</p></div></div>
-<div class="section">
+<li><code>--resume-from</code> - resumes a reactor the specified project (e.g. when it fails in the middle)</li>
+<li><code>--also-make</code> - build the specified projects, and any of their dependencies in the reactor</li>
+<li><code>--also-make-dependents</code> - build the specified projects, and any that depend on them</li>
+<li><code>--fail-fast</code> - the default behavior - whenever a module build fails, stop the overall build immediately</li>
+<li><code>--fail-at-end</code> - if a particular module build fails, continue the rest of the reactor and report all failed modules at the end instead</li>
+<li><code>--non-recursive</code> - do not use a reactor build, even if the current project declares modules and just build the project in the current directory</li></ul>
+<p>Refer to the Maven command line interface reference for more information on these switches.</p></section></section><section>
<h3><a name="More_information"></a>More information</h3>
<ul>
-<li><a class="externalLink" href="http://books.sonatype.com/mvnex-book/reference/multimodule.html"> Chapter 6. A Multi-module Project (Maven by Example)</a></li></ul></div></div>
+<li><a class="externalLink" href="http://books.sonatype.com/mvnex-book/reference/multimodule.html"> Chapter 6. A Multi-module Project (Maven by Example)</a></li></ul></section></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-multiple-repositories.html
==============================================================================
--- maven/website/content/guides/mini/guide-multiple-repositories.html (original)
+++ maven/website/content/guides/mini/guide-multiple-repositories.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-multiple-repositories.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-multiple-repositories.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,7 +160,7 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Setting_up_Multiple_Repositories"></a>Setting up Multiple Repositories</h2>
<p>There are two different ways that you can specify the use of multiple repositories. The first way is to specify in a POM which repositories you want to use:</p>
<div class="source"><pre class="prettyprint linenums">
@@ -182,7 +182,7 @@
</project>
</pre></div>
<p><b>NOTE:</b> You will also get the standard set of repositories as defined in the <a href="../introduction/introduction-to-the-pom.html#Super_POM">Super POM</a>.</p>
-<p>The other way you can specify the use of multiple repositories by creating a profile in your <tt>${user.home}/.m2/settings.xml</tt> file like the following:</p>
+<p>The other way you can specify the use of multiple repositories by creating a profile in your <code>${user.home}/.m2/settings.xml</code> file like the following:</p>
<div class="source"><pre class="prettyprint linenums">
<settings>
...
@@ -207,13 +207,13 @@
...
</settings>
</pre></div>
-<p>If you specify repositories in profiles you must remember to activate that particular profile! As you can see above we do this by registering a profile to be active in the <tt>activeProfiles</tt> element.</p>
+<p>If you specify repositories in profiles you must remember to activate that particular profile! As you can see above we do this by registering a profile to be active in the <code>activeProfiles</code> element.</p>
<p>You could also activate this profile on the command like by executing the following command:</p>
<div class="source"><pre class="prettyprint linenums">
mvn -Pmyprofile ...
</pre></div>
-<p>In fact the <tt>-P</tt> option will take a CSV list of profiles to activate if you wish to activate multiple profiles simultaneously.</p>
-<p><b>Note</b>: The settings descriptor documentation can be found on the <a href="../../maven-settings/settings.html">Maven Local Settings Model Website</a>.</p></div>
+<p>In fact the <code>-P</code> option will take a CSV list of profiles to activate if you wish to activate multiple profiles simultaneously.</p>
+<p><b>Note</b>: The settings descriptor documentation can be found on the <a href="../../maven-settings/settings.html">Maven Local Settings Model Website</a>.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-naming-conventions.html
==============================================================================
--- maven/website/content/guides/mini/guide-naming-conventions.html (original)
+++ maven/website/content/guides/mini/guide-naming-conventions.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-naming-conventions.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-naming-conventions.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -120,18 +120,18 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_to_naming_conventions_on_groupId.2C_artifactId.2C_and_version"></a>Guide to naming conventions on groupId, artifactId, and version</h2>
<ul>
<li><b>groupId</b> uniquely identifies your project across all projects. A group ID should follow <a class="externalLink" href="https://docs.oracle.com/javase/specs/jls/se6/html/packages.html#7.7">Java's package name rules</a>. This means it starts with a reversed domain name you control. For example,
-<p><tt>org.apache.maven</tt>, <tt>org.apache.commons</tt></p>
+<p><code>org.apache.maven</code>, <code>org.apache.commons</code></p>
<p>Maven does not enforce this rule. There are many legacy projects that do not follow this convention and instead use single word group IDs. However, it will be difficult to get a new single word group ID approved for inclusion in the Maven Central repository.</p>
-<p>You can create as many subgroups as you want. A good way to determine the granularity of the <tt>groupId</tt> is to use the project structure. That is, if the current project is a multiple module project, it should append a new identifier to the parent's <tt>groupId</tt>. For example,</p>
-<p><tt>org.apache.maven</tt>, <tt>org.apache.maven.plugins</tt>, <tt>org.apache.maven.reporting</tt></p></li>
+<p>You can create as many subgroups as you want. A good way to determine the granularity of the <code>groupId</code> is to use the project structure. That is, if the current project is a multiple module project, it should append a new identifier to the parent's <code>groupId</code>. For example,</p>
+<p><code>org.apache.maven</code>, <code>org.apache.maven.plugins</code>, <code>org.apache.maven.reporting</code></p></li>
<li><b>artifactId</b> is the name of the jar without version. If you created it, then you can choose whatever name you want with lowercase letters and no strange symbols. If it's a third party jar, you have to take the name of the jar as it's distributed.
-<p>eg. <tt>maven</tt>, <tt>commons-math</tt></p></li>
+<p>eg. <code>maven</code>, <code>commons-math</code></p></li>
<li><b>version</b> if you distribute it, then you can choose any typical version with numbers and dots (1.0, 1.1, 1.0.1, ...). Don't use dates as they are usually associated with SNAPSHOT (nightly) builds. If it's a third party artifact, you have to use their version number whatever it is, and as strange as it can look. For example,
-<p><tt>2.0</tt>, <tt>2.0.1</tt>, <tt>1.3.1</tt></p></li></ul></div>
+<p><code>2.0</code>, <code>2.0.1</code>, <code>1.3.1</code></p></li></ul></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-new-committers.html
==============================================================================
--- maven/website/content/guides/mini/guide-new-committers.html (original)
+++ maven/website/content/guides/mini/guide-new-committers.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-new-committers.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-new-committers.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -120,12 +120,12 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Guide_for_new_commiters"></a>Guide for new commiters</h2>
<p>First thing is to sort out some administrative tasks. Before your account is created and commit access granted you must complete and fax back to Apache the <a class="externalLink" href="http://www.apache.org/licenses/#clas">Committer's License Agreement</a>.</p>
<p>While this process is sorting itself out it is recommended that you peruse the various guides provided by Apache. All the guides are located in the <a class="externalLink" href="http://www.apache.org/dev/">Development Infrastructure Information</a>.</p>
<p>Of particular interest is the <a class="externalLink" href="http://www.apache.org/dev/committers.html">Committer's FAQ</a> and the <a class="externalLink" href="http://www.apache.org/dev/new-committers-guide.html">New Committer's Guide</a>.</p>
-<p>If you have any questions please feel free to ask any of the Maven developers.</p></div>
+<p>If you have any questions please feel free to ask any of the Maven developers.</p></section>
</div>
</div>
</div>
Modified: maven/website/content/guides/mini/guide-proxies.html
==============================================================================
--- maven/website/content/guides/mini/guide-proxies.html (original)
+++ maven/website/content/guides/mini/guide-proxies.html Sun Jun 9 13:59:34 2019
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<!--
- | Generated by Apache Maven Doxia Site Renderer 1.8.1 from content/apt/guides/mini/guide-proxies.apt at 2019-06-09
+ | Generated by Apache Maven Doxia Site Renderer 1.9 from content/apt/guides/mini/guide-proxies.apt at 2019-06-09
| Rendered using Apache Maven Fluido Skin 1.7
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
@@ -160,10 +160,10 @@
</div>
</div>
<div id="bodyColumn" class="span10" >
-<div class="section">
+<section>
<h2><a name="Configuring_a_proxy"></a>Configuring a proxy</h2>
<p>You can configure a proxy to use for some or all of your HTTP requests with Maven. The username and password are only required if your proxy requires basic authentication (note that later releases may support storing your passwords in a secured keystore - in the mean time, please ensure your settings.xml file (usually ${user.home}/.m2/settings.xml) is secured with permissions appropriate for your operating system).</p>
-<p>The <tt>nonProxyHosts</tt> setting accepts wild cards, and each host not to proxy is separated by the | character. This matches the JDK configuration equivalent.</p>
+<p>The <code>nonProxyHosts</code> setting accepts wild cards, and each host not to proxy is separated by the | character. This matches the JDK configuration equivalent.</p>
<div class="source"><pre class="prettyprint linenums">
<settings>
.
@@ -184,12 +184,11 @@
.
</settings>
</pre></div>
-<p>Please note that currently NTLM proxies are not supported as they have not been tested. You may be able to use the relevant system properties on JDK 1.4+ to make this work.</p>
-<div class="section">
+<p>Please note that currently NTLM proxies are not supported as they have not been tested. You may be able to use the relevant system properties on JDK 1.4+ to make this work.</p><section>
<h3><a name="Resources"></a>Resources</h3>
<ol style="list-style-type: decimal">
<li><a href="../../maven-settings/settings.html">Settings descriptor documentation</a></li>
-<li><a href="./guide-configuring-maven.html">Configuring Maven</a></li></ol></div></div>
+<li><a href="./guide-configuring-maven.html">Configuring Maven</a></li></ol></section></section>
</div>
</div>
</div>