svn commit: r782373 - /maven/site/trunk/src/site/apt/developers/release/releasing.apt

[ba...@apache.org]

Author: baerrach
Date: Sun Jun  7 11:49:33 2009
New Revision: 782373

URL: http://svn.apache.org/viewvc?rev=782373&view=rev
Log:
Added to Prerequisites GPG client, Subversion client, JDK 1.4.2 and MAVEN_OPTS environment variable

Added a verification section before running the release process

Fixed the snapshot repository url used to verify the snapshot deploy

Updated [[5]] Close the staging repository to the new UI.
TODO: take new snapshots.

Updated the JIRA link to use Oustanding issues since this will include re-opened issues.

Added commit your changes to [[13]] Update the maven site

Added a trouble shooting section.

Modified:
    maven/site/trunk/src/site/apt/developers/release/releasing.apt

Modified: maven/site/trunk/src/site/apt/developers/release/releasing.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/developers/release/releasing.apt?rev=782373&r1=782372&r2=782373&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/developers/release/releasing.apt (original)
+++ maven/site/trunk/src/site/apt/developers/release/releasing.apt Sun Jun  7 11:49:33 2009
@@ -36,6 +36,16 @@
   {{{../committer-settings.html}Committer settings}}.
 
   * you have created your GPG keys. For more information, please refer to {{{pmc-gpg-keys.html}Making GPG Keys}}.
+  
+  * you have a GPG client installed and on your shell's path. See {{{http://www.gnupg.org/}http://www.gnupg.org/}}.
+  
+  * you have a Subversion 1.5+ client installed and on your shell's path. See {{{http://subversion.tigris.org/}http://subversion.tigris.org/}}.
+  
+  * you have a Java 1.4.2 JDK installed and on your shell's path. See {{{http://java.sun.com/j2se/1.4.2/download.html}http://java.sun.com/j2se/1.4.2/download.html}}.
+  
+  * you have set the environment variable MAVEN_OPTS=-Xmx512m 
+  
+  []
 
  Formerly, a <<<release>>> profile was required in the <<<$\{user.home\}/.m2/settings.xml>>> to define the staging
  repository. As of inheritance from the Apache parent POM version 5, a repository manager will automatically handle
@@ -68,6 +78,17 @@
 
 %{snippet|id=release-profile|url=http://svn.apache.org/repos/asf/maven/pom/trunk/asf/pom.xml}
 
+* Verify you are using JDK 1.4.2
+
+  Maven 2.0.X and its plugins should be built with JDK 1.4.2.
+
++-----+
+>mvn --version
+...
+Maven version: 2.0.X
+Java version: 1.4.2_18
++-----+
+
 * Release Process for Part Of Maven
 
  [[1]] Prepare your POMs for release:
@@ -114,7 +135,7 @@
  <<Note:>> You should verify the deployment under Maven Snapshot repository on Apache.
 
 +-----+
-https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-XXX-plugin/Y.Z-SNAPSHOT/
+https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-XXX-plugin/Y.Z-SNAPSHOT/
 +-----+
 
  [[3]] Prepare the release
@@ -137,9 +158,9 @@
 
  [[5]] Close the staging repository
 
- Login to <<<{{https://repository.apache.org}}>>> using your Apache SVN credentials. Click on "Staging Repositories". Then click
+ Login to <<<{{https://repository.apache.org}}>>> using your Apache SVN credentials. Click on "Staging". Then click
  on "org.apache.maven" in the list of repositories. In the panel below you should see an open repository that is linked
- to your username and ip. Right click on this repository and select "Finish". This will close the repository from future
+ to your username and ip. Right click on this repository and select "Close". This will close the repository from future
  deployments and make it available for others to view. If you are staging multiple releases together, skip this step
  until you have staged everything.
 
@@ -230,8 +251,8 @@
  To get the JIRA release notes link, browse to the plugin's JIRA page, select the <Road Map> link,
  and use the link to <Release Notes> that is next to the version being released.
 
- To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <Project Summary>
- on the right, use the link for <Open> issues.
+ To get the list of issues left in JIRA, browse to the plugin's JIRA page, and from the <Preset Filters>
+ on the right, use the link for <Outstanding> issues.
 
  [[9]] Check the vote results
 
@@ -320,6 +341,8 @@
 
  If this is a shared component release, update the version number for the
  component on the <src/site/apt/shared/index.apt> page.
+ 
+ Commit your changes.
 
  [[14]] Update JIRA
 
@@ -389,3 +412,37 @@
  <<Note:>> If you don't have access to edit this page email <<<"Jason van Zyl" <ja...@maven.org>>>>
 
  [[18]] Celebrate :o)
+ 
+Trouble Shooting
+
+* mvn release:prepare "commit failed" during <<<Prepare the release>>>
+
+  If you get an error message similar to:
+
++-----+
+    [INFO] Unable to tag SCM
+    Provider message:
+    The svn tag command failed.
+    Command output:
+    svn: Commit failed (details follow):
+    svn: File '/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.7/src/main/java/org/apache/maven/plugin/eclipse/EclipsePlugin.java' already exists
++-----+
+
+  Then the resolution is to use a Subversion client 1.6+ and to run <<<svn update>>>.
+  
+* mvn release:prepare "commit failed" during <<<Prepare the release>>>
+
+  If you get an error message similar to:
+
++-----+
+[ERROR] BUILD FAILURE
+[INFO] ------------------------------------------------------------------------
+[INFO] Unable to tag SCM
+Provider message:
+The svn tag command failed.
+Command output:
+svn: Path 'https://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.7' already exists
++-----+
+
+  Then the resolution is to delete the tag using <<<svn del -m "re-releasing build" <svn path>>>> 
+  
\ No newline at end of file