crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-581) Remove dependency on Guava
Date Mon, 07 Dec 2015 22:14:11 GMT

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

Sean Owen commented on CRUNCH-581:
----------------------------------

Projects like Spark do depend on Guava, they just shade it. Mostly -- Spark also had the very
unfortunate bad luck to have used a Guava class in a public API, which means that bit can't
be shading and ends up meaning there is a lesser version of the same dependency conflict possible.

I'd suggest seeing how far shading gets you. The Spark assembly pom has a fairly clear specimen
of how to do it.

> Remove dependency on Guava
> --------------------------
>
>                 Key: CRUNCH-581
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-581
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Micah Whitacre
>            Assignee: Josh Wills
>
> As mentioned on CRUNCH0-356, we should look at removing all dependencies on Guava to
help simplify Crunch's dependency tree and to not constrain consumers on the versions of Guava
they want to consume.
> Looking at other projects like Spark, Hadoop, and HBase they all do not depend on Guava
but have copied a class or two internally that they depend on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message