guava-gwt should publish Gradle module metadata or somehow fix POM about guava HOT 2 CLOSED

The thing is that GWT loads everything from its own classpath when you run the compiler or codeserver, so for the GWT tooling itself you'd rather use the runtime dependencies (I'm not sure it makes much difference, I haven't checked though); and this also applies to other dependencies that "enhance" the compilation (through GWT generator and linker mechanisms), particularly their transitive dependencies that might not be GWT-aware.
Indeed ideally we'd want the union of compile-time and runtime dependencies but I'm not sure whether this is even possible with Gradle. This artifact being specific for use with GWT though, making sure both sets of dependencies are equivalent sounds like the safest approach: whichever consuming projects will use, they'll have all they need.

from guava.

Sorry for not getting to this sooner. Thanks for the easy repro. I have a fix on the way in #7153.

It does seem interesting that GWT would use the "runtime" configuration for its compilation. I guess GWT's runtime and compile time aren't as cleanly separable, since the output of compilation contains exactly what will be used at runtime. I could maybe see having GWT us "compile-time" instead (as an acknowledgment that some people like to omit source-retention annotations at runtime), but I could also believe that that causes problems of its own. And maybe there's a way to use the union of those, but maybe that causes problems, too :) Anyway, I'm happy to just fix it on our end.

from guava.