[
https://issues.apache.org/jira/browse/HBASE-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985429#action_12985429
]
Charles Oliver Nutter commented on HBASE-3374:
----------------------------------------------
Ryan: I understand what ASF needs, and that's exactly what I want to provide.
Of the libraries that are GPL, according to our COPYING file:
* jvm-language-runtime is not shipped with JRuby binaries. It is used only
because it provides a mock JSR-292 invokedynamic library for compile-time on
JVMs that do not have JSR-292 (Java 6 and lower).
* jffi could potentially be relicensed, or simply removed; it is for native
library access, and JRuby would work correctly without it.
* jgrapht-jdk15 is only used by a newer in-development compiler that is not
used normally, and could be removed. We would like to explore replacements.
* we do not ship JNA anymore
Of these, only jffi and jgrapht are in the binaries we distribute, and it's
likely JRuby would work with them just yanked out. If any of the other
libraries are included in our binaries, it's a bug in our build process.
If we provide a build of JRuby that does not include those GPLed libraries,
would that satisfy ASF's requirements?
> 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.
