[maven-site] branch master updated: formatting

[hb...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new ede1a13  formatting
ede1a13 is described below

commit ede1a13f533b21444b061800e8c5963b8add9f2a
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sun Sep 5 18:26:39 2021 +0200

    formatting
---
 .../development/guide-testing-development-plugins.apt  | 16 ++++------------
 .../apt/guides/development/guide-testing-releases.apt  | 18 +++++++++---------
 2 files changed, 13 insertions(+), 21 deletions(-)

diff --git a/content/apt/guides/development/guide-testing-development-plugins.apt b/content/apt/guides/development/guide-testing-development-plugins.apt
index b8a5a43..ba0f898 100644
--- a/content/apt/guides/development/guide-testing-development-plugins.apt
+++ b/content/apt/guides/development/guide-testing-development-plugins.apt
@@ -49,7 +49,7 @@ Guide to Testing Development Versions of Plugins
 
   The first step is to include this in your project:
 
--------
++-------
 <project>
   ...
   <pluginRepositories>
@@ -60,7 +60,7 @@ Guide to Testing Development Versions of Plugins
   </pluginRepositories>
   ...
 </project>
--------
++-------
 
   After this is included, there are three ways to use the updated versions:
 
@@ -70,26 +70,18 @@ Guide to Testing Development Versions of Plugins
 
     * You can have Maven automatically check for updates on a given interval, for example:
 
--------
++-------
 <project>
   ...
   <pluginRepositories>
     <pluginRepository>
       <id>apache.snapshots</id>
       <url>https://repository.apache.org/snapshots/</url>
-      <!-- The releases element here is due to an issue in Maven 2.0 that will be
-           fixed in future releases. This should be able to be disabled altogether. -->
-      <releases>
-        <updatePolicy>daily</updatePolicy>
-      </releases>
-      <snapshots>
-        <updatePolicy>daily</updatePolicy>
-      </snapshots>
     </pluginRepository>
   </pluginRepositories>
   ...
 </project>
--------
++-------
 
   <Note:> These last two techniques mean that <every> plugin will be updated to the latest snapshot version.
 
diff --git a/content/apt/guides/development/guide-testing-releases.apt b/content/apt/guides/development/guide-testing-releases.apt
index 237e428..3909cb8 100644
--- a/content/apt/guides/development/guide-testing-releases.apt
+++ b/content/apt/guides/development/guide-testing-releases.apt
@@ -47,7 +47,7 @@ Guide to Testing Staged Releases
 
   The repository configuration for testing a plugin will typically look something like this (it will be provided in the vote email):
 
-----
++----
   ...
   <pluginRepositories>
     <pluginRepository>
@@ -56,7 +56,7 @@ Guide to Testing Staged Releases
     </pluginRepository>
   </pluginRepositories>
   ...
-----
++----
 
   The important thing is that the staged release does not pollute your eventual environment as it may change if the vote fails and the 
   release is made again. This is why clearing the local repository is necessary, but if you are using a repository manager this is also
@@ -111,7 +111,7 @@ Guide to Testing Staged Releases
   If you are using the repository mirroring technique to lock down to the repository manager in your environment, you would add an additional
   mirror to correspond to the additional repository in the POM, such as:
 
-----
++----
   ...
   <mirror>
     <id>staged-releases-mirror</id>
@@ -119,14 +119,14 @@ Guide to Testing Staged Releases
     <mirrorOf>staged-releases</mirrorOf>
   </mirror>
   ...
-----
++----
 
 * Using a Settings Profile
 
   If you regularly test staged releases and want to have a more convenient way to add the repository to a build without
-  modifying your POM, you may add a profile to your POM:
+  modifying your POM, you may add a profile to your <<<~/.m2/settings.xml>>>:
 
-----
++----
   ...
   <profiles>
     <profile>
@@ -139,14 +139,14 @@ Guide to Testing Staged Releases
       </pluginRepositories>
     </profile>
   ...
-----
++----
 
   With this in place, you can activate it by simply changing the plugin version to the one you are testing in the POM as above, then
   run the build with the following command:
 
-----
++----
 mvn verify -Pstaged-releases
-----
++----
 
   Note that the same conditions apply as above about cleaning out the local repository to prevent pollution of your local build
   environment.