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

Mike Drob commented on HBASE-16196:
-----------------------------------

bq. Can we continue to ship a complete jruby jar?
Yea, we can ship all of those, assuming I don't find anything else. EPL and 
Ruby License are both on the [Category 
B|https://www.apache.org/legal/resolved.html#category-b] list. The JRuby works 
are tri-licensed and explicitly called out as acceptable in the next question 
on that page as well.

bq. Out of interest, how much as the jruby complete grown since 1.6.x?
{noformat}
-rw-rw-r-- 1 mdrob mdrob 14M Nov  4  2014 jruby-complete-1.6.8.jar
-rw-rw-r-- 1 mdrob mdrob 22M Jun  8  2016 jruby-complete-1.7.17.jar
-rw-rw-r-- 1 mdrob mdrob 22M May  1 14:19 jruby-complete-9.1.8.0.jar
{noformat}
+8M since 1.6.8, but most of that came in 1.7.x so there's not anything to be 
gained with a smaller version increment in terms of size.

> Update jruby to a newer version.
> --------------------------------
>
>                 Key: HBASE-16196
>                 URL: https://issues.apache.org/jira/browse/HBASE-16196
>             Project: HBase
>          Issue Type: Bug
>          Components: dependencies, shell
>            Reporter: Elliott Clark
>            Assignee: Mike Drob
>            Priority: Critical
>             Fix For: 2.0.0, 1.5.0
>
>         Attachments: 0001-Update-to-JRuby-9.1.2.0-and-JLine-2.12.patch, 
> hbase-16196.branch-1.patch, hbase-16196.v2.branch-1.patch, 
> hbase-16196.v3.branch-1.patch, hbase-16196.v4.branch-1.patch, 
> HBASE-16196.v5.patch, HBASE-16196.v6.patch
>
>
> Ruby 1.8.7 is no longer maintained.
> The TTY library in the old jruby is bad. The newer one is less bad.
> Since this is only a dependency on the hbase-shell module and not on 
> hbase-client or hbase-server this should be a pretty simple thing that 
> doesn't have any backwards compat issues.



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

Reply via email to