This message was deleted.

Is it safe to assume that you are on Gradle 5.3 or newer?

8.0.1

Then it should usually just work. Is maybe something suspicious or enlightning logged on

--info

or

--debug

level?

Yeah, I checked the logs before, nothing interesting there and wanted to actually avoid debugging. But I debugged it eventually and it turned out gradle also cached the metadata. We just fixed our proxy server that previously wasn’t serving the

.module

files, so gradle resorted to regular POMs. But now when we fixed our proxy server gradle still had the old metadata cached locally and didn’t even try to resolve them again. Removing metadata caches from

.gradle

dir helped.

Great, or

--refresh-dependencies

would probably also have helped. 🙂

Good to know that one, yeah, thanks