svn commit: r921766 - in /websites/staging/olingo/trunk/content: ./ doc/release.html

[bu...@apache.org]

Author: buildbot
Date: Wed Sep 10 12:12:10 2014
New Revision: 921766

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/doc/release.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Sep 10 12:12:10 2014
@@ -1 +1 @@
-1623950
+1623977

Modified: websites/staging/olingo/trunk/content/doc/release.html
==============================================================================
--- websites/staging/olingo/trunk/content/doc/release.html (original)
+++ websites/staging/olingo/trunk/content/doc/release.html Wed Sep 10 12:12:10 2014
@@ -244,7 +244,7 @@ Of course the Release Manager can also u
 <li>Release candidate maven artifacts are promoted in the Apache Maven Repository and 
 made available <a href="https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~~~~">here</a>.</li>
 <li>Publish final release Version to <a href="https://repository.apache.org/">Apache Repository</a><ul>
-<li>First publish via <code>mvn deploy -Papache.release</code> into the <em>Staging Area</em></li>
+<li>First publish via <code>mvn deploy -Papache-release</code> into the <em>Staging Area</em></li>
 <li>From <em>Staging Area</em> close and release the staged Artifacts to finish publishing </li>
 <li>Afterwards the Maven artifacts are automatically synced to <a href="http://search.maven.org/#search|ga|1|org.apache.olingo">Maven Central</a>.</li>
 </ul>