hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3374) Our jruby jar has *GPL jars in it; fix
Date Mon, 20 Dec 2010 23:57:01 GMT

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

stack commented on HBASE-3374:

So, 1.0.3. is still available in maven repos.  Thats good.  java_import is not available in
1.0.3.  Thats the 'safe' way of doing imports --- see http://jira.codehaus.org/browse/JRUBY-3171.
 Using raw 'import' seems to work but dumps out the following before shell starts if the referenced
import is used more than once -- e.g. if we're using HConstants defines in a few places in
.rb code:

(eval):1 warning: already initialized constant HConstants

Fully specifying java classes with packages in all places they are used seems to get rid of
the above.  I'm working on a patch to do that.

We will have to remove TestShell.  It uses facility only available in later jrubys.

Looking at the way the shell was refactored by Alexei, its kinda nice the way he did it. 
All of the java access is done in one or two files apart from the bulk of the ruby code; makes
it easier doing this fixup.

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

View raw message