hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Oliver Nutter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3374) Our jruby jar has *GPL jars in it; fix
Date Sun, 23 Jan 2011 22:34:47 GMT

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

Charles Oliver Nutter commented on HBASE-3374:
----------------------------------------------

FYI, I have taken this to be a JRuby issue, and filed the following: http://jira.codehaus.org/browse/JRUBY-5410

I want us to publish a *GPL-free maven artifact for JRuby 1.6.0. This should be usable by
Apache and other projects that can't include GPLed code.

I am talking to the maintainer of jffi (and jaffl, which was incorrectly listed as MIT licensed
in COPYING) about adding an Apache-friendly license.

I added a jar-jruby-nogpl target to our build.xml and fixed COPYING to properly reflect jaffl
licensing and jffi and jaffl homepages

I also confirmed that simply removing jffi, jaffl, and jgrapht from jruby.jar does not damage
general Ruby behavior. As mentioned above, some native or system-level capabilities are disabled
or work differently, but IRB, RubyGems, and Rails all function correctly.

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


Mime
View raw message