[jira] Commented: (HBASE-3374) Our jruby jar has *GPL jars in it; fix

["stack (JIRA)" <ji...@apache.org>]

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

stack commented on HBASE-3374:
------------------------------

Closing.  Opened HBASE-3600 to accomodate update to jruby 1.6.0RC2 (Charles, if you see this, I notice that 1.6.0RC2 is out but its not in a maven repo -- you know why?  Usually RCs make it to maven it would seem.  Thanks, and thanks again for fixing licensing so we could use the new stuff again)

> 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
>             Fix For: 0.92.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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira