Offline build using dynamic version failing

Help/Discuss
1

Our artefact server is down, so we’re running gradle --offline but I’m still unable to build using my local gradle cache due to:

:mycode:main: No cached version listing for com.mycompany:my-dependency:3.0.0.+ available for offline mode.

I know in my local gradle cache I have my-dependency:3.0.0.28 - so why doesn’t it find this?
I know it has something to do with the dynamic version ‘+’ …

2

To resolve a dynamic version Gradle requests the maven-metadata.xml where the versions are listed and then picks from there.

As your error message says “No cached version listing”, I guess that file is, what it does not have in cache and thus cannot proceed.

3

I think you’re right! - I hadn’t made the connection to a “…version listing” being the cached maven-metadata.xml file. I suspect that my cache had exceeded its TTL but as I was then offline it couldn’t get another one. Is there a simple way to continue to work offline in this situation i.e. don’t clear this file from the cache or use an older one?

4

I have no idea.
But I think “use an older one” does not make sense as they are not versioned, so if it is not there, it is not there.
I’d expect it to not be e purged from the cache if used recently, if not used recently it could have been cleaned from the cache, and gone is gone I guess. :man_shrugging:

If you did recently use it but still it is gone now, maybe you found a bug? No idea.

5

Configuring the dependency cache ttl can be done via

configurations.all {
    resolutionStrategy.cacheChangingModulesFor 4, 'hours'
}
configurations.all {
    resolutionStrategy.cacheDynamicVersionsFor 10, 'minutes'
}

see Dependency Caching.

As for the missing listing, you may temporarily try to pinpoint the exact version that you have locally cached to continue (aka replace the dynamic version with the concrete one), depending on the amount this may get tedious but maybe better than being completely cut off from development.

6

How should changing the TTL help?
If it is in the cache and --offline it hopefully is used even if the TTL expired.
But in OP case it says it is not present in the cache.