Build.gradle does not seem to respect custom repositories

Help/Discuss Plugin Portal
1

Hi!

I was using mavenCentral() and gradlePluginPortal() until I hit the rate limit issue.
Beyond IPs: Addressing organizational overconsumption in Maven Central.
So, we use an internal artifactory proxy server which is a mirror of mavencentral().
I donot specify any plugin related settings.
build.gradle content looks like this:

import java.text.SimpleDateFormat

plugins {
    id 'groovy'
    id 'jacoco'
    id 'org.sonarqube' version "5.1.0.4882"
}


jacocoTestReport {
    group = 'Reporting'
    reports {
        xml.required = true
    }
}

repositories {
    maven {
        url = uri("https://artifactory.com/maven-central-remote")
        credentials {
            username = findProperty('artifactory_user') ?: System.getenv('ARTIFACTORY_USER')
            password = findProperty('artifactory_password') ?: System.getenv('ARTIFACTORY_PASSWORD')
        }
    }
}

dependencies {
    implementation 'org.codehaus.groovy:groovy:2.4.21'
    implementation 'org.codehaus.groovy:groovy-xml:2.4.21'
    implementation 'org.codehaus.groovy:groovy-json:2.4.21'
    implementation 'com.cloudbees:groovy-cps:1.31'
    implementation 'com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.15.2'
}

Especially, for sonarqube it still tries to fetch from:
Could not get resource ‘https://plugins.gradle.org/m2/org/sonarsource/scanner/api/sonar-scanner-api/2.16.2.588/sonar-scanner-api-2.16.2.588.pom’.

What have I missed?
Its probably the namespace but how to fix it?
Also, I do not understand why does it hit the default mavenCentral() or gradlePluginPortal() inspite of not specifying it.
Moreover, I have not provided anything in settings.gradle.
Could you please help me understand what have I missed?

Thanks!

Thanks!

2

Moreover, I have not provided anything in settings.gradle.

That’s the point.
The repository you defined is for you project dependencies, not for the plugins you use.
For that you use pluginManagement { repositories { ... } } in your settings script which defaults to the plugin portal. And that in turn redirects to Maven Central for stuff it does not serve itself.

3

Thank you for replying !
I did not use settings.gradle as here it is mentioned as optional if you donot have sub-projects.

Now, I have this in settings.gradle:

pluginManagement {
    repositories {
        maven {
        url = uri("https://artifactory.com/maven-central-remote")
        credentials {
            username = System.getenv('ARTIFACTORY_USER')
            password = System.getenv('ARTIFACTORY_PASSWORD')
        }
	}
    }
}

I run behind a corporate proxy and so far it does not seem to find:

Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
 Included Builds (No included builds contain this plugin)
 Plugin Repositories (could not resolve plugin artifact 'org.sonarqube:org.sonarqube.gradle.plugin:5.1.0.4882')
4

Why are the versions different in : Central Repository: org/sonarsource/sonarqube/sonarqube and https://plugins.gradle.org/m2/org/sonarqube/org.sonarqube.gradle.plugin/ ?

5

I did not use settings.gradle as here it is mentioned as optional if you donot have sub-projects.

It is optional, but actually it is bad practice not to have one.
Each build should have a settings file.
Otherwise for example the project name of the root project is determined by the directory in which the project lives currently and the project name is for example used as default name for artifacts you build and so on.

I run behind a corporate proxy and so far it does not seem to find:

Sure, why should it if you only mirror Maven Central?
Most plugins are hosted in Gradle Plugin Portal, not on Maven Central.
So if you only mirror Maven Central, the plugin is of course not available in your mirror.

Why are the versions different in : Central Repository: org/sonarsource/sonarqube/sonarqube and https://plugins.gradle.org/m2/org/sonarqube/org.sonarqube.gradle.plugin/ ?

Why not?
Those are totally different artifacts that have nothing to do with each other.