Last week, the maven repository we use for snapshots went down due to a hardware failure. Unfortunately, it went down late at night and the morning after some of our developers tried to build. Since the ttl was up, gradle tried to download the new artifacts but was unable to reach the nexus repository. Once the build had failed, they tried to build using --offline but were unable to build as gradle complained about not having the artifact, despite the artifact sitting in the filestore. After some more testing, it seems that gradle keeps metadata information in another directory and will invalidate the file in the filestore before checking to see if it can access the repository. Thus, when trying to build offline, gradle will complain about not having the artifact.

Is this the desired behavior or do we have the configuration of the repository wrong? Is there a workaround to this other than setting the snapshot ttl to a long time and only grabbing the latest dependencies with --refresh-dependencies?

We currently set the ttl to 30 minutes for snapshot dependencies and are running with gradle 1.0 with linux and windows machines.