The writing was on the wall for that one for a few years now. Quoting from the guava documentation for at least several releases going back a few years (I picked this one at random from a release a year ago):
Warning: We recommend against using CheckedFuture in new projects. CheckedFuture is difficult to build libraries atop. CheckedFuture ports of methods like Futures.transformAsync(com.google.common.util.concurrent.ListenableFuture<I>, com.google.common.util.concurrent.AsyncFunction<? super I, ? extends O>) have historically had bugs, and some of these bugs are necessary, unavoidable consequences of the CheckedFuture API. Additionally, CheckedFuture encourages users to take exceptions from one thread and rethrow them in another, producing confusing stack traces. That... sounds... familiar... A. On Wed, 25 Jan 2017 21:40:43 +0100 Robert Varga <[email protected]> wrote: > Hello everyone, > > this is a heads-up for upcoming Guava API change which affects our > APIs. > > CheckedFuture is being removed from Guava in February 2018, according > to: > https://google.github.io/guava/releases/snapshot/api/docs/com/google/common/util/concurrent/CheckedFuture.html. > > That means that we are going to have to stick with old Guava or break > our API contract in parts affecting a lot of projects. > > I think we need to evaluate the impact during Nitrogen planning, at > least to understand the impact this is going to have. > > I have filed https://bugs.opendaylight.org/show_bug.cgi?id=7683 to > track this task. > > Regards, > Robert > _______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
