From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

build scan or `./gradlew dependencyInsight --configuration compileClasspath --dependency com.google.code.findbugs:jsr305`?

Guava now publishes Gradle Metadata.

Unfortunately something was done wrong during publishing. The metadata is broken and points at the wrong parent (some SNAPSHOT version) that contains the versions of the transitive dependencies. This could very likely cause this.

<https://github.com/google/guava/issues/6612>

I would skip this version and wait for a fix release

For me this didn’t fix the problem….. build still hangs and crashes with OOM

The dependencyInsight command fails with the following error:
```* What went wrong:
configuration 'compileClasspath' not found in configuration container.```

The only difference with the new `32.1.1-jre` version is that we get this additional error:
```The dependency resolution engine wasn't able to find a version of module com.google.j2objc:j2objc-annotations which satisfied all requirements because the graph wasn't stable enough. The highest version was selected in order to stabilize selection.
Features available in a stable graph like version alignment are not guaranteed in this case.```

Okay then this is probably related to bugs in this area as I commented on the issue you created. I gave more context there:
<https://github.com/gradlex-org/java-ecosystem-capabilities/issues/55#issuecomment-1615564599>

ok, but the build hangs even when we don’t use the java-ecosystem-capabilities plugin.