[
https://issues.apache.org/jira/browse/HBASE-20108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382362#comment-16382362
]
Mike Drob commented on HBASE-20108:
-----------------------------------
bq. How do you run out of the dev tree
After {{mvn package}} you can run {{bin/hbase}} directly.
We generate some classpaths at
https://github.com/apache/hbase/blob/master/hbase-assembly/pom.xml#L109 and
then dev-tree classpaths are built in
https://github.com/apache/hbase/blob/master/bin/hbase#L321
> `hbase zkcli` falls into a non-interactive prompt after HBASE-15199
> -------------------------------------------------------------------
>
> Key: HBASE-20108
> URL: https://issues.apache.org/jira/browse/HBASE-20108
> Project: HBase
> Issue Type: Bug
> Components: Usability
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-20108.001.branch-2.patch,
> HBASE-20108.002.branch-2.patch
>
>
> HBASE-15199 pulls the jruby-complete jar out of the normal classpath for
> commands run in HBase. Jruby-complete bundles jline inside. ZK uses jline for
> its nice shell-like usage.
> The problem is that this uncovered a bug where we're not explicitly bundling
> a version of jline to make sure that {{hbase zkcli}} actually works. As long
> as we're expecting {{zkcli}} to be there, we should provide jline on the
> classpath to make sure the users get a real cli.
> Thanks to [~sergey.soldatov] for getting to the bottom of it quickly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
