You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/02/01 17:59:39 UTC

[jira] [Created] (HBASE-15199) Move jruby jar so only on hbase-shell module classpath; currently globally available

stack created HBASE-15199:
-----------------------------

             Summary: 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: jruby, shell
            Reporter: stack


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.4#6332)