Gradle - disable *all* non-local caching

[foggy anchor]

what can I do to tell gradle "do not under any circumstances cache anything to do with this project anywhere other than within the project directory, nor access those external caches for anything related to this project"?

I'm getting really fed up with having to go and clear things out manually.

I've just done it now; rm -rf the gradle directory in my home directory.
Before I did this, several of my dependencies simply weren't installed - the files did not exist anywhere on my computer.
I ran ./gradlew build, ./gradlew clean build, ./gradlew downloadAssets, a variety of other scripts, and messed around in IDEA for a while, and gradle just comes back with "oh! I have those cached! I don't need to do anything".
After deleting that directory, whaddaya know, it's finally figured out it needs to download those missing dependencies.

I have to do this at least once when I switch to a different project. On this computer I have only ever used provided gradlew files, I have never used the global gradle command directly. I don't have any gradle configuration of any kind other than what is in the projects themselves. I've now used gradle on three different computers, one mac and two linux, and in all cases I have had this exact issue, and the only fix is exactly what I've described. The issue happens regardless of what project I'm working on, what version of gradle, what version of java.

Note that I do not mean just the build cache. I mean anything gradle does on the filesystem outside of my project which fits the vaguest definition of "caching".

Usually I'm a fan of smart build tool caching, but in gradle's case it's a buggy mess that causes more problems than it solves. How do I get rid of it forever?

[fallow surge]

<@&987246399047479336> please have a look, thanks.

[vast arch]

Have you told intellij to use gradlew in the project (instead of the gradle installed on your system.) I usually never have to use the system gradle install.

If you have some build problem you can delete the gradle cache folder.

If this is something you ahve to do alot then there is something wrong with your build script or more likely, a plugin.

[dark bolt]

if you want to not cache specifically dependencies, this doesn't make a lot of sense unless you want it specifically for dynamic (2.+) or changing (2.0.0-SNAPSHOT) versions
in which case, you can specify in in the build file:

configucations.all {
    resolutionStrategy {
        cacheDynamicVersionsFor(...)
        cacheChangingVersionsFor(...)
    }
}

@foggy anchor

for well-behaved static artifacts, not wanting to cache probably means there's something wrong in the development process