[ 
https://issues.apache.org/jira/browse/HBASE-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847880#action_12847880
 ] 

Kay Kay commented on HBASE-2255:
--------------------------------

| @Kay Kay I'm trying out the zk 3.3.0 RC0. Once release, then we should move 
TRUNK to pull zk from maven repo or are you thinking sooner?

sure, of course - we can wait for the 3.3.0 to be released and then try out the 
new version. I was just cross-linking information here, since the zk team seems 
to be very close to 3.3.0 , with release notes etc. prepared. So - we can leave 
it as it is and then revisit sometime later. 

| The thrift we're pulling is http://people.apache.org/~psmith/hbase/repo. 
Yeah, the pom is off because at a minimum we've discovered it requires sfl4j. 
How you suggest we fix it? Update the pom for thrift in paul's repo?

I think updating the pom in paul's repo seems like the right thing to do, so 
that everybody who need to use thrift can benefit from that.  Also , it would 
be useful to publish the artifacts under org.apache.hbase groupId to a snapshot 
repository so that it is more public. 

long term, anybody with good offices with the thrift team can gently nudge them 
towards publishing it themselves ;) . Even if they are reluctant to publishing 
artifacts, committing that patch alone would suffice since that will make it a 
lot more easy to publish artifacts ourselves, by using the source tree. 







> take trunk back to hadoop 0.20
> ------------------------------
>
>                 Key: HBASE-2255
>                 URL: https://issues.apache.org/jira/browse/HBASE-2255
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: ryan rawson
>            Assignee: ryan rawson
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2255.patch
>
>
> revert the dependency on hadoop 0.21, back to hadoop 0.20 (we hardly knew ye)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to