opendev/gerrit
Code Issues Proposed changes

Fix documentation of how to publish artifacts to Maven Central

Browse Source 
The preparations for publishing to the Google Cloud Storage are not
needed anymore.

Change-Id: I306de581fb30fa2bcacfacdc9de29194a5d9793f
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
This commit is contained in:
Edwin Kempin
2014-05-26 23:42:42 +02:00
parent e9f81cf76d
commit 76afac60b7
1 changed files with 1 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Documentation/dev-release.txt
View File

@@ -141,7 +141,7 @@ for the Subproject in `/lib/BUCK` to the released version.
==== Publish the Extension and Plugin API Jars ==== Publish the Extension and Plugin API Jars
* Make sure you have done the * Make sure you have done the
link:dev-release-deploy-config.html#deploy-configuration-settings-xml[ link:dev-release-deploy-config.html#deploy-configuration-setting-maven-central[
configuration needed for deployment] configuration needed for deployment]
* Push the Jars to the Maven Central: * Push the Jars to the Maven Central:
@@ -150,11 +150,6 @@ configuration needed for deployment]
buck build api_deploy buck build api_deploy
---- ----
* Make sure you have done the
link:dev-release-deploy-config.html#deploy-configuration-setting-maven-central[
configuration needed for deployment]
* Troubleshooting: to see the commands that are execured in Buck build process * Troubleshooting: to see the commands that are execured in Buck build process
environment variable VERBOSE can be set: environment variable VERBOSE can be set:
+ +