svn commit: r628544 - /maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt

[br...@apache.org]

Author: brett
Date: Sun Feb 17 12:14:50 2008
New Revision: 628544

URL: http://svn.apache.org/viewvc?rev=628544&view=rev
Log:
updated instructions for testing staged releases easily

Modified:
    maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt

Modified: maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt?rev=628544&r1=628543&r2=628544&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt (original)
+++ maven/site/trunk/src/site/apt/guides/development/guide-testing-releases.apt Sun Feb 17 12:14:50 2008
@@ -14,14 +14,14 @@
   
   The steps are as follows:
 
-    * add the repository or plugin repository to your POM (see below)
+    * add the repository or plugin repository to your POM or settings (see below)
 
     * ensure you are using the version being released of the artifacts in your project,
       e.g. by setting the <<<\<version\>>>> in the <<<\<plugin\>>>> tag.
 
     * test the release
 
-    * remove the repository from your POM
+    * remove the repository from your POM if it was specified there
 
     * remove the artifacts from your local repository when you have completed testing
 
@@ -31,7 +31,7 @@
   ...
   <pluginRepositories>
     <pluginRepository>
-      <id>staged.releases</id>
+      <id>staged-releases</id>
       <url>http://people.apache.org/~dfabulich/stage-repo</url>
     </pluginRepository>
   </pluginRepositories>
@@ -82,7 +82,11 @@
   <<<http://localhost:8080/archiva/repository/staged-releases/>>>.
 
   The advantage of this approach is that you can usually remove your entire local repository afterwards and after removing the staged repository
-  from your POM the artifacts will no longer be used.
+  from your POM the artifacts will no longer be used. There is no need to remove the repository or artifacts from Archiva itself - unless a
+  staged release is updated for further testing.
+
+  It is also quite easy to test another staged release at a later date by reusing the repository, or adding a proxy connector and remote
+  repository for a different staging repository.
 
   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:
@@ -97,4 +101,33 @@
   ...
 ----
 
+* 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:
+
+----
+  ...
+  <profiles>
+    <profile>
+      <id>staged-releases</id>
+      <pluginRepositories>
+        <pluginRepository>
+          <id>staged-releases</id>
+          <url>http://people.apache.org/~dfabulich/stage-repo</url>
+        </pluginRepository>
+      </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 clean install -Pstaged-releases
+----
+
+  Note that the same conditions apply as above about cleaning out the local repository to prevent pollution of your local build
+  environment.