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

Ted Yu commented on HBASE-15199:
--------------------------------

This was what I did:
. produced hbase-2.0.0-SNAPSHOT-bin.tar.gz
. expanded the tar ball under /tmp
. made sure JRUBY_HOME points to a directory where lib/jruby.jar exists (copied 
from jruby-complete jar)
. used the following command to launch shell:
{code}
 JRUBY_HOME=/xx/jruby bin/hbase shell
{code}
I got:
{code}
LoadError: no such file to load -- irb/completion
  require at org/jruby/RubyKernel.java:1062
   (root) at /tmp/hbase-2.0.0-SNAPSHOT/bin/../bin/hirb.rb:41
{code}
What did I miss ?

> Move jruby jar so only on hbase-shell module classpath; currently globally 
> available
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-15199
>                 URL: https://issues.apache.org/jira/browse/HBASE-15199
>             Project: HBase
>          Issue Type: Task
>          Components: dependencies, jruby, shell
>            Reporter: stack
>            Assignee: Xiang Li
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: 15199.txt, HBASE-15199.master.001.patch, 
> HBASE-15199.master.002.patch, HBASE-15199.master.003.patch
>
>
> A suggestion that came up out of internal issue (filed by Mr Jan Van Besien) 
> was to move the scope of the jruby include down so it is only a dependency 
> for the hbase-shell. jruby jar brings in a bunch of dependencies (joda time 
> for example) which can clash with the includes of others. Our Sean suggests 
> that could be good to shut down exploit possibilities if jruby was not 
> globally available. Only downside I can think is that it may no longer be 
> available to our bin/*rb scripts if we move the jar but perhaps these can be 
> changed so they can find the ruby jar in new location.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to