You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2017/04/06 17:46:42 UTC

[jira] [Commented] (HADOOP-14284) Shade Guava everywhere

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

Andrew Wang commented on HADOOP-14284:
--------------------------------------

This is pretty similar to something [~busbey] and I discussed, I like it!

One nit suggestion: simplify name to hadoop-shaded-thirdparty?

> Shade Guava everywhere
> ----------------------
>
>                 Key: HADOOP-14284
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14284
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0-alpha3
>            Reporter: Andrew Wang
>            Priority: Blocker
>         Attachments: HADOOP-14238.pre001.patch
>
>
> HADOOP-10101 upgraded the guava version for 3.x to 21.
> Guava is broadly used by Java projects that consume our artifacts. Unfortunately, these projects also consume our private artifacts like {{hadoop-hdfs}}. They also are unlikely on the new shaded client introduced by HADOOP-11804, currently only available in 3.0.0-alpha2.
> We should shade Guava everywhere to proactively avoid breaking downstreams. This isn't a requirement for all dependency upgrades, but it's necessary for known-bad dependencies like Guava.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org