Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <22636490.163781295895164803.JavaMail.jira@thor>
Date: Mon, 24 Jan 2011 13:52:44 -0500 (EST)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-3375) Move away from jruby; build our
 shell elsewise either on another foundation or build up our own
In-Reply-To: <14314059.199011292739960683.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-3375:
------------------------------

@Jim The javascript shell was poor compared to IRB when I tested this stuff out a good while back (See HBASE-487 for my blunderings).

> Move away from jruby; build our shell elsewise either on another foundation or build up our own
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3375
>                 URL: https://issues.apache.org/jira/browse/HBASE-3375
>             Project: HBase
>          Issue Type: Task
>          Components: shell
>            Reporter: stack
>             Fix For: 0.92.0
>
>
> JRuby has been sullied; its been shipping *GPL jars with a while now.  A hack up to remove these jars is being done elsewhere (HBASE-3374).  This issue is about casting our shell anew atop a foundation that is other than JRuby or writing a shell of our own from scratch.
> JRuby has gotten us this far.  It provides a shell and it also was used scripting HBase.  It would be nice if we could get scripting and shell in the redo.
> Apart from the licensing issue above and that the fix will be reverting our JRuby to a version that is no longer supported and that is old, other reasons to move off JRuby are that while its nice having ruby to hand when scripting, the JRuby complete jar is 10 or more MB in size.  Its bloated at least from our small shell perspective.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.