Could not resolve org.apache.maven:maven-settings-builder:3.0.5e

I try to do a gradle (5.4.1) build by using plugins and repositories below
plugins {
id ‘application’
id ‘maven-publish’
id ‘net.linguica.maven-settings’ version ‘0.5’
id ‘org.sonarqube’ version ‘2.8’
}
repositories {
mavenCentral()
maven {
url = ‘https://artifactory/third-party-snapshots
}
}

Though I’m using mavencentral build is failing with connection time out error

but got failed with below error
* What went wrong:
A problem occurred configuring root project 
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not resolve org.apache.maven:maven-settings:3.0.5.
     Required by:
         project : > net.linguica.maven-settings:net.linguica.maven-settings.gradle.plugin:0.5 > net.linguica.gradle:maven-settings-plugin:0.5
      > Skipped due to earlier error
   > Could not resolve org.apache.maven:maven-settings-builder:3.0.5.
     Required by:
         project : > net.linguica.maven-settings:net.linguica.maven-settings.gradle.plugin:0.5 > net.linguica.gradle:maven-settings-plugin:0.5
      > Could not resolve org.apache.maven:maven-settings-builder:3.0.5.
         > **Could not get resource 'https://plugins.gradle.org/m2/org/apache/maven/maven-settings-builder/3.0.5/maven-settings-builder-3.0.5.pom'.**
**            > Could not HEAD 'https://jcenter.bintray.com/org/apache/maven/maven-settings-builder/3.0.5/maven-settings-builder-3.0.5.pom'.**
**               > Connect to jcenter.bintray.com:443 [jcenter.bintray.com/34.95.74.180] failed: connect timed out**
   > Could not resolve org.apache.maven:maven-model-builder:3.0.5.

change url = ‘https://artifactory/third-party-snapshots’ to url ‘https://plugins.gradle.org/m2/’ and try

That has nothing to do with that artifact repository or any of the declared repositories, as those repositories are for project dependencies, not for resolving plugins.

As you can see in the error message plugins.gradle.org is exactly where it tried to resolve the plugin dependency.

Either JCenter was just down at the time you tried, or the computer where you tried to run this is not allowed to connect to JCenter.