You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shindig.apache.org by li...@apache.org on 2010/05/11 08:36:33 UTC

svn commit: r943012 - /shindig/site/trunk/src/site/apt/community/releasing.apt

Author: lindner
Date: Tue May 11 06:36:33 2010
New Revision: 943012

URL: http://svn.apache.org/viewvc?rev=943012&view=rev
Log:
s/release/apache-release/g

Modified:
    shindig/site/trunk/src/site/apt/community/releasing.apt

Modified: shindig/site/trunk/src/site/apt/community/releasing.apt
URL: http://svn.apache.org/viewvc/shindig/site/trunk/src/site/apt/community/releasing.apt?rev=943012&r1=943011&r2=943012&view=diff
==============================================================================
--- shindig/site/trunk/src/site/apt/community/releasing.apt (original)
+++ shindig/site/trunk/src/site/apt/community/releasing.apt Tue May 11 06:36:33 2010
@@ -57,7 +57,7 @@ Apache Shindig Release Process
 
   [[2]] Check that your POMs will not lose content when they are rewritten during the release process.
 
-    [[A]] <<<mvn release:prepare -DdryRun=true -Prelease>>>
+    [[A]] <<<mvn release:prepare -DdryRun=true -Papache-release>>>
 
     [[B]] Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has
       been removed. The only things that should be different between these files are the <version> and <scm> elements.
@@ -73,13 +73,13 @@ Apache Shindig Release Process
   Next, prepare the release by calling Maven:
 
 +-----+
-mvn release:clean -Prelease
-mvn release:prepare -Prelease
+mvn release:clean -Papache-release
+mvn release:prepare -Papache-release
 +-----+
 
   <<Notes>>:
 
-    [[1]] <-Prelease> is <<very>> important since <<<assembly>>> and <<<samples>>> modules are not included by
+    [[1]] <-Papache-release> is <<very>> important since <<<assembly>>> and <<<samples>>> modules are not included by
       default in the build (for productivity reasons).
 
     [[2]] Preparing the release will create a new tag in SVN, automatically checking in on your behalf. Verify the
@@ -96,7 +96,7 @@ mvn release:prepare -Prelease
   Call Maven to publish the generated artifacts:
 
 +-----+
-mvn release:perform -Prelease
+mvn release:perform -Papache-release
 +-----+
 
   <<Note>>: All artifacts will be signed and pushed to {{https://repository.apache.org/}}.