From 1f02fffd044245fe777c2194517234950d530b35 Mon Sep 17 00:00:00 2001 From: Jerry He Date: Sun, 3 May 2015 12:05:59 -0700 Subject: [PATCH] HBASE-13598 Make hbase assembly attach to the project: doc addendum --- src/main/asciidoc/_chapters/developer.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/main/asciidoc/_chapters/developer.adoc b/src/main/asciidoc/_chapters/developer.adoc index 1fbf8a376c3..ee03614ab33 100644 --- a/src/main/asciidoc/_chapters/developer.adoc +++ b/src/main/asciidoc/_chapters/developer.adoc @@ -636,8 +636,7 @@ Release needs to be tagged for the next step. . Deploy to the Maven Repository. + -Next, deploy HBase to the Apache Maven repository, using the `apache-release` profile instead of the `release` profile when running the +mvn - deploy+ command. +Next, deploy HBase to the Apache Maven repository, using the `apache-release` profile instead of the `release` profile when running the `mvn deploy` command. This profile invokes the Apache pom referenced by our pom files, and also signs your artifacts published to Maven, as long as the _settings.xml_ is configured correctly, as described in <>. + [source,bourne] @@ -648,6 +647,8 @@ $ mvn deploy -DskipTests -Papache-release + This command copies all artifacts up to a temporary staging Apache mvn repository in an 'open' state. More work needs to be done on these maven artifacts to make them generally available. ++ +We do not release HBase tarball to the Apache Maven repository. To avoid deploying the tarball, do not include the `assembly:single` goal in your `mvn deploy` command. Check the deployed artifacts as described in the next section. . Make the Release Candidate available. +