[
https://issues.apache.org/jira/browse/HBASE-15199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998488#comment-15998488
]
Sean Busbey edited comment on HBASE-15199 at 5/5/17 3:49 PM:
-------------------------------------------------------------
I think more experienced operators can already manually change things such that
JRuby stuff ends up in the server environment. We should stay focused on the
path everyone ends up walking down by default.
[~water], would you mind putting together the change? An addendum is fine, but
if it looks like things will take until sometime next week, then let's do a new
JIRA instead.
was (Author: busbey):
I think more experience operators can already manually change things such that
JRuby stuff ends up in the server environment. We should stay focused on the
path everyone ends up walking down by default.
[~water], would you mind putting together the change? An addendum is fine, but
if it looks like things will take until sometime next week, then let's do a new
JIRA instead.
> 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)
