I think this change is important enough to warrant a breaking version bump.
Virtually every project depends on Guava, and Flume should certainly
shade/rename Guava for its internal use.

I'd be on board with doing a Flume 2.0 to remove Guava from the public API.

Mike

On Mon, Jan 29, 2018 at 2:31 AM, Denes Arvay <[EMAIL PROTECTED]> wrote: