> There's something severely wrong with your setup if you can't get stable maven or gradle builds
To be fair with OP, I had a similar experience in the previous company. Sometimes after bumping a dependency or something, even if you asked IntelliJ to "Reload All Gradle Projects" something wouldn't work and I needed to restart the IDE. Not saying it was common, but it did happen. This was a Kotlin codebase.
Now working in a company using Scala, I had a few cases where IntelliJ failed to resolve a dependency correctly so it was saying that the class I just created didn't exist (this was in shared library and two different dependencies pulled it, but we did pin the dependency directly and sbt was building it correctly, it was only IntelliJ that was becoming confused). Cleaning up the build sometimes worked, sometimes didn't, but even when it worked it would go back after a while. Eventually we updated all dependencies in all projects and it now always works, but it was painful for a while.
To be fair with OP, I had a similar experience in the previous company. Sometimes after bumping a dependency or something, even if you asked IntelliJ to "Reload All Gradle Projects" something wouldn't work and I needed to restart the IDE. Not saying it was common, but it did happen. This was a Kotlin codebase.
Now working in a company using Scala, I had a few cases where IntelliJ failed to resolve a dependency correctly so it was saying that the class I just created didn't exist (this was in shared library and two different dependencies pulled it, but we did pin the dependency directly and sbt was building it correctly, it was only IntelliJ that was becoming confused). Cleaning up the build sometimes worked, sometimes didn't, but even when it worked it would go back after a while. Eventually we updated all dependencies in all projects and it now always works, but it was painful for a while.