By using the URL Chris showed below, I was able to run hbase test suite (0.98 branch) against zookeeper 3.4.8 RC0
[INFO] Apache HBase - Shell ............................... SUCCESS [02:29 min] [INFO] Apache HBase - Integration Tests ................... SUCCESS [ 1.647 s] [INFO] Apache HBase - Examples ............................ SUCCESS [ 8.915 s] [INFO] Apache HBase - Assembly ............................ SUCCESS [ 2.306 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:32 h [INFO] Finished at: 2016-02-06T21:12:24-08:00 w.r.t. the staging URL, maybe in the future, giving root of the staging repository in RC announcement is enough. Below is an example from hadoop 2.6.4 RC announcement: https://repository.apache.org/content/repositories/orgapachehadoop-1028 <https://repository.apache.org/content/repositories/orgapachehadoop-1028/?> using which I was able to run hbase test suite directly. Cheers On Sat, Feb 6, 2016 at 1:33 PM, Chris Nauroth <[email protected]> wrote: > Hi Ted, > > I was able to build HBase trunk against the ZooKeeper 3.4.8 release > candidate with the following change: > > diff --git a/pom.xml b/pom.xml > index ccc7eb5..4e67ec1 100644 > --- a/pom.xml > +++ b/pom.xml > @@ -3044,5 +3044,9 @@ > <name>project</name> > <url>file:${project.basedir}/src/main/site/resources/repo</url> > </repository> > + <repository> > + <id>zookeeper RC</id> > + <url>https://repository.apache.org/content/groups/staging</url> > + </repository> > </repositories> > </project> > > Note that the repository URL cannot contain the full path to the ZooKeeper > release candidate. Instead, the URL needs to point to the root of the > repository, and then Maven will try to look up artifacts relative to that > URL. > > > Thank you for taking the release candidate for a spin! > > --Chris Nauroth > > > > > On 2/6/16, 9:47 AM, "Ted Yu" <[email protected]> wrote: > > >With this change in pom.xml : > > > >diff --git a/pom.xml b/pom.xml > >index 0b7e38a..62d2214 100644 > >--- a/pom.xml > >+++ b/pom.xml > >@@ -394,6 +394,14 @@ > > <url>https://repository.apache.org/content/repositories/releases/ > ></url> > > </repository> > > <repository> > >+ <id>apache RC</id> > >+ <url> > >https://repository.apache.org/content/repositories/orgapachehadoop-1028 > ></url> > >+ </repository> > >+ <repository> > >+ <id>zookeeper RC</id> > >+ <url> > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/ > >zookeeper/3.4.8/ > ></url> > >+ </repository> > >+ <repository> > > <id>java.net</id> > > <name>Java.Net</name> > > <url>http://download.java.net/maven/2/</url> > > > >I got: > > > >[ERROR] Failed to execute goal on project hbase-common: Could not resolve > >dependencies for project > >org.apache.hbase:hbase-common:jar:0.98.17-SNAPSHOT: Could not find > >artifact > > org.apache.zookeeper:zookeeper:jar:3.4.8 in apache release ( > >https://repository.apache.org/content/repositories/releases/) -> [Help 1] > > > >Did I specify the staging repo incorrectly ? > > > >On Fri, Feb 5, 2016 at 8:00 PM, Raúl Gutiérrez Segalés > ><[email protected]> > >wrote: > > > >> This is a bugfix release candidate for 3.4.8. It fixes 9 issues, most > >> notably a deadlock when shutting down ZooKeeper. > >> > >> The full release notes is available at: > >> > >> > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801 > >>&version=12326517 > >> > >> *** Please download, test and vote by February 20th 2016, 23:59 UTC+0. > >>*** > >> > >> Source files: > >> http://people.apache.org/~rgs/zookeeper-3-4-8-rc0/ > >> > >> Maven staging repo: > >> > >> > >> > https://repository.apache.org/content/groups/staging/org/apache/zookeeper > >>/zookeeper/3.4.8/ > >> > >> The tag to be voted upon: > >> https://svn.apache.org/repos/asf/zookeeper/tags/release-3.4.8-rc0 > >> > >> ZooKeeper's KEYS file containing PGP keys we use to sign the release: > >> http://www.apache.org/dist/zookeeper/KEYS > >> > >> Should we release this candidate? > >> > >> Note that the approval is by lazy majority according to the bylaws and > >>only > >> PMC votes are binding. > >> > >> > >> -rgs > >> > >
