[
https://issues.apache.org/jira/browse/HBASE-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985423#action_12985423
]
Charles Oliver Nutter commented on HBASE-3374:
----------------------------------------------
Woah there cowboys!
Downgrading to JRuby 1.0.3 is a *TERRIBLE* idea. 1.0.3 does not include a
compiler, and performs somewhere in the neighborhood of 50-100 times worse than
current JRuby versions. It also has much worse compatibility with Ruby, is not
compatible at all with Ruby 1.8.7 or 1.9, and has many other leaks, bugs, and
flaws.
We would happily work with you guys (and Apache proper) to either publish a
version of JRuby that does not include the offending libraries, or try to get
the creator of those libraries (who is a JRuby committer) to relicense them.
I would STRONGLY recommend undoing the massive damage you will cause by
downgrading to JRuby 1.0.3 and working with us to get you a "safe" version of a
more current JRuby.
> Our jruby jar has *GPL jars in it; fix
> --------------------------------------
>
> Key: HBASE-3374
> URL: https://issues.apache.org/jira/browse/HBASE-3374
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.90.0
>
> Attachments: jruby.txt
>
>
> The latest JRuby's complete jar bundles *GPL jars (JNA and JFFI among
> others). It looks like the functionality we depend on -- the shell in
> particular -- makes use of these dirty jars so they are hard to strip. They
> came in because we (I!) just updated our JRuby w/o checking in on what
> updates contained. JRuby has been doing this for a while now (1.1.x added
> the first LGPL). You have to go all the ways back to the original HBase
> checkin, HBASE-487, of JRuby -- 1.0.3 -- to get a JRuby w/o *GPL jars.
> Plan is to try and revert our JRuby all the ways down to 1.0.3 before
> shipping 0.90.0. Thats what this issue is about.
> We should also look into moving off JRuby in the medium to long-term. Its
> kinda awkward sticking on an old version that is no longer supported. I'll
> open an issue for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
