Move graph functionality to a separate module and maven artifact about guava HOT 2 CLOSED

Unfortunately, mixing a new version of com.google.common.graph with older versions of other Guava packages will likely lead to runtime errors, since common.graph probably relies on APIs that were added in newer Guava versions.

(There are also some additional problems that would arise if we split Guava after having released it as a full jar for all these years. And even if we'd released it as separate jars all this time, that could lead to issues, too, especially since Maven doesn't resolve version conflicts in favor of the newest version.)

Your best bet is probably to download a new Guava and have a took like Proguard or jarjar rewrite it to a new package, preserving only common.graph and its needed dependencies. (You'd likely also have it "hide" those dependencies by moving them into common.graph as package-private or by giving them an unappealing package name.) Then you could use com.yourcompany.guavagraph.

Also: If there's anything worth sharing about your difficulties with updating Guava, let us know. We know that our past habit of removing APIs was a big cause of problems until ~6 years ago, but we also know that random small problems can break things and force rollbacks. There might well not be much we can do, but let us know if you think otherwise.

from guava.

@cpovirk thank you for the the response and suggestions

from guava.