Kevin, I think we should remove those classes.
We may run into compatibility issues in future — or, as in this case, want to use features that are in a version of a library or the JDK that not all of our users are happy to upgrade to — and if so, we can always resurrect the files from git history. Julian > On Sep 9, 2018, at 9:16 AM, Vladimir Sitnikov <[email protected]> > wrote: > > Kevin>I think that means that both Compatible and CompatibleGuava11 can be > removed since they should no longer be used. > > Could we keep the files as a monument to Guava's version policy? > > Vladimir
