hbase-issues mailing list archives

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

Date

Fri, 05 May 2017 01:54:04 GMT

[ https://issues.apache.org/jira/browse/HBASE-15199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-15199:
--------------------------------
The original patch correctly accounts for JRUBY_HOME, no need for an
addendum.
Ted, it sounds like you should bring the s3 issue up on the jira that got
marked as a DUP of this one. The problem is the same before and after.
> 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)