[
https://issues.apache.org/jira/browse/HADOOP-14238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950364#comment-15950364
]
Andrew Wang commented on HADOOP-14238:
--------------------------------------
Since HADOOP-10101 was committed, is the plan to finish this investigation,
then shade Guava everywhere?
A more sure way of finding API pollution would be writing a bytecode analysis
tool. We'd filter for classes and methods annotated IA.Public and
LimitedPrivate, then check those method signatures for Guava class references.
Another possible quick thing you could try is using JACC or JDiff to compare
current vs. shaded Guava.
> [Umbrella] Rechecking Guava's object is not exposed to user-facing API
> ----------------------------------------------------------------------
>
> Key: HADOOP-14238
> URL: https://issues.apache.org/jira/browse/HADOOP-14238
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Tsuyoshi Ozawa
> Priority: Critical
>
> This is reported by [~hitesh] on HADOOP-10101.
> At least, AMRMClient#waitFor takes Guava's Supplier instance as an instance.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
