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

Hudson commented on HBASE-5412:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #164 (See 
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/164/])
    HBASE-5412 HBase book, section 2.6.4, has deficient list of client 
dependencies (Revision 1381894)

     Result = FAILURE
stack : 
Files : 
* /hbase/trunk/src/docbkx/configuration.xml

                
> HBase book, section 2.6.4, has deficient list of client dependencies
> --------------------------------------------------------------------
>
>                 Key: HBASE-5412
>                 URL: https://issues.apache.org/jira/browse/HBASE-5412
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 0.92.0
>            Reporter: Mike Spreitzer
>            Assignee: Ian Varley
>            Priority: Minor
>              Labels: documentation
>             Fix For: 0.96.0
>
>         Attachments: HBASE-5412.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> The current text in section 2.6.4 of the HBase book says this about client 
> dependencies:
> Minimally, a client of HBase needs the hbase, hadoop, log4j, commons-logging, 
> commons-lang, and ZooKeeper jars in its CLASSPATH connecting to a cluster.
> I tried that, and got an exception due to a class not being found.  I fixed 
> that by searching for that class in the jars in lib/, and tried again.  Got 
> an exception, due to a different class not found.  I iterated until it 
> worked.  When I was done, I found myself using the following JARs:
> commons-configuration-1.6.jar  hadoop-core-1.0.0.jar  slf4j-api-1.5.8.jar
> commons-lang-2.5.jar           hbase-0.92.0.jar       slf4j-log4j12-1.5.8.jar
> commons-logging-1.1.1.jar      log4j-1.2.16.jar       zookeeper-3.4.2.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to