[GRADLE-3216] Using changing provided by component metadata rule for latest.release fails to resolve module Created: 16/Dec/14 Updated: 19/Mar/15 Resolved: 19/Mar/15
|Reporter:||Benjamin Muschko||Assignee:||Benjamin Muschko|
In the following build script, we try to resolve the latest release version of a dependency from an Ivy repository. The dependency can have one of the statuses "snapshot" or "release". The snapshot version indicates a changing version. The changing flag is set by a component metadata rule. The TTL for changing versions is set to 0 seconds.
The first resolution of the dependency works fine. On every succeeding resolution, Gradle fails with the following exception:
This works fine if the command line option --refresh-dependencies is used.