Hmm, I tried setting cacheChangingModulesFor 0, “seconds” for my configuration and it didn’t seem to work.Here’s what I’m doing:
Component B depends on Component A version 1.0.
Resolving the configuration caches Component A version 1.0, great.
Component A version 1.0 is then updated in the repository to include an additional artifact. Resolving the configuration again doesn’t update Component A version 1.0 in the cache.
Using --refresh-dependencies does the trick. How does Gradle know the dependency has changed?