Revision history [back]

There could be several reasons why Gradle encounters an issue in retrieving an external dependency from a local artifactory that is meant to be downloaded from Maven Central. Some possible reasons include:

1. The dependency may not be present in the local artifactory or may not have been properly configured in the artifactory. In this case, Gradle will not be able to download the dependency from the artifactory and will need to fetch it from Maven Central instead.

2. There could be a configuration issue with Gradle or the artifactory that is preventing the dependency from being retrieved properly. For example, Gradle may not be configured to look for dependencies in the artifactory or the artifactory may not be properly configured to allow Gradle to access it.

3. There could be a network issue that is preventing Gradle from accessing the artifactory or Maven Central. This could be due to firewall restrictions, network outages, or other network-related issues that are preventing Gradle from downloading the dependency.

In order to troubleshoot the issue, it is important to check the configuration of both Gradle and the artifactory, verify that the dependency is present in the artifactory, and ensure that there are no network issues that are preventing Gradle from accessing the artifactory or Maven Central.