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

ryan rawson commented on HBASE-3374:
------------------------------------

Based on COPYING from:
https://github.com/jruby/jruby/blob/master/COPYING

The following libraries are a problem:

 build_lib/jffi*jar (http://kenai.com/projects/jffi) and
 build_lib/jgrapht-jdk1.5.jar (http://jgrapht.sourceforge.net) are
 distributed under the GPL v3.

 build_lib/jna*jar (http://jna.dev.java.net) are distributed
 under the LGPL-2.1+ license.

 build_lib/invokedynamic.jar and build_lib/jsr292-mock.jar
 (http://code.google.com/p/jvm-language-runtime) are distributed
 under the LGPL license.


Also there are a few broken links such as 
http://projectkenai.com/projects/jaffl which are a little concerning.





> 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.

Reply via email to