IntelliJ occasionally thinks a gradle managed JAR file dependency is empty. No combination of replacing the JAR on disk, synchronizing, restarting, or clearing IntelliJ caches resolves the issue, so I believe it doesn't like something about the JAR file itself.
In the project tree:
As you would expect, imports from the JAR's packages fail.
Yet, the JAR files are not empty, and compilations outside of the IntelliJ tool chain work fine.
Does IntelliJ have some strict requirement about JAR contents, formatting, or encoding which may be causing this?