hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16196) Update jruby to a newer version.
Date Wed, 03 May 2017 23:36:04 GMT

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

Mike Drob commented on HBASE-16196:

Sure, I can take a shot at fixing the licensing docs.

Most of it looks pretty straightforward. That said, I know jruby-complete bundles jline (BSD
3-clause) but I don't see any references to it in their COPYING. This leads me to wonder what
_else_ they bundle that isn't explicitly listed. I'll leave notes here so my work can be double
checked later.

Cracking open the jruby-complete jar, I find the following jars (with the following licenses)

I suspect that all of the unknowns are also using the same EPL/GPL/LGPL combo.

The only bundled javascript I could find is Darkfish (BSD-3) which bundles jQuery (MIT).

The jruby COPYING claims to include a bunch of ASLv2 things: maven, jnr-constants, joda-time,
jffoi, jnr-ffi, jnr-enxio, jnr-unixsocket, jnr-netdb, nailgun.
However, I can't find most of those in the jruby-complete jar.

The whole license thing is a mess.

> Update jruby to a newer version.
> --------------------------------
>                 Key: HBASE-16196
>                 URL: https://issues.apache.org/jira/browse/HBASE-16196
>             Project: HBase
>          Issue Type: Bug
>          Components: dependencies, shell
>            Reporter: Elliott Clark
>            Assignee: Mike Drob
>            Priority: Critical
>             Fix For: 2.0.0, 1.5.0
>         Attachments: 0001-Update-to-JRuby-, hbase-16196.branch-1.patch,
hbase-16196.v2.branch-1.patch, hbase-16196.v3.branch-1.patch, hbase-16196.v4.branch-1.patch,
> Ruby 1.8.7 is no longer maintained.
> The TTY library in the old jruby is bad. The newer one is less bad.
> Since this is only a dependency on the hbase-shell module and not on hbase-client or
hbase-server this should be a pretty simple thing that doesn't have any backwards compat issues.

This message was sent by Atlassian JIRA

View raw message