ff317d0d7f
We have faked some Ivy repositories on a few artifact locations. Today when Gradle attempts to resolve these artifacts, it follows its default strategy to search for Gradle metadata, then Maven POM files, then Ivy descriptors, and finally will fallback to looking directly for the artifact. This wastes times on remote network calls that will 404 anyway since these metadata resources will not exist for these fake Ivy repositories. This commit overrides the Gradle strategy to look directly for artifacts. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||