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

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

    [ https://issues.apache.org/jira/browse/PHOENIX-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004493#comment-14004493 ] 

James Taylor commented on PHOENIX-993:
--------------------------------------

+1. Thanks, [~gabriel.reid]. I agree completely -we shouldn't pull in this dependency. Should we also file an HBase bug, as we should be able to have a dependency on HBase without requiring jruby?

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