You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/05/22 10:15:40 UTC

[jira] [Resolved] (PHOENIX-993) Remove/exclude JRuby dependency

     [ https://issues.apache.org/jira/browse/PHOENIX-993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid resolved PHOENIX-993.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1
                   3.1
                   5.0.0

Pushed to 3.0, 4.0, and master branches.

I looked into logging the underlying issue as a bug upstream in HBase. In HBase 0.98+, JRuby is only included in test dependencies, so all is well there. In HBase 0.94, there's only one exported hbase jar (which needs JRuby), so it doesn't seem to be possible to skip it in any way.

> Remove/exclude JRuby dependency
> -------------------------------
>
>                 Key: PHOENIX-993
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-993
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>             Fix For: 5.0.0, 3.1, 4.1
>
>         Attachments: PHOENIX-993-3.0.patch, PHOENIX-993-master.patch
>
>
> Phoenix 3.0 pulls in org.jruby:jruby-complete transitively (via HBase), and Phoenix 4.0 explicitly includes jruby-complete as a dependency.
> JRuby is used by HBase to provide shell functionality. However, jruby-complete is an uber jar that includes things like joda-time and jline. These "invisible" dependencies can cause difficult to debug classpath issues in downstream applications.
> The transitive dependency to jruby should be excluded in 3.0, and the explicit (and transitive?) dependency should also be removed/excluded in 4.0 and master.



--
This message was sent by Atlassian JIRA
(v6.2#6252)