Repository settings not honored

Describe the bug

Gradle repositories can be configured to expose only specific groups / artifacts, e.g., with:

repositories {
    mavenCentral()
    jcenter {
        content {
            includeGroup("org.jetbrains.kotlinx")
        }
    }
}

JCenter should only get used to retrieve artifacts with group org.jetbrains.kotlinx

Apparently, however, refreshVersions seems not to be honoring the setup. Try for instance:

dependencies {
    implementation("org.eclipse.mylyn.github:org.eclipse.egit.github.core:_")
}

Latest version on Central (at the moment of writing) is 2.1.5.

refreshVersions detects version 3.4.0.201406110918-r, which is not available.

version.org.eclipse.mylyn.github..org.eclipse.egit.github.core=2.1.5
##                                                 # available=3.4.0.201406110918-r

To Reproduce

An example is provided in this PR: https://github.com/DanySK/upgradle/pull/8 The build fails, Gradle (legitimately) does not find the updated artifact: https://travis-ci.com/github/DanySK/upgradle/jobs/301834976

Commenting out the jcenter repo declaration makes the plugin work as expected.

Expected behavior No update is suggested, due to the repository configuration

Additional context If needed, I can produce a minimal example starting from the repo in which I’m having issues, but the problem should be quite well isolated already. Let me know

[LouisCAD]

Hi @DanySK, thanks manifesting! I knew that it was a feature we don’t currently support but was wondering if it’d actually bother anyone.

I’ll revisit this issue after #153 is resolved, to see if after the behavior change, the issue is still important to address, and how we can address it best.

Regarding your bot, that’s very cool, please open an issue or reach out on Kotlin’s Slack (channel linked from a badge in README) when you have something to show! I know some people like @martinbonnin will be interested!

[LouisCAD]

I’ll do my best to ensure we never rely on a Gradle internal API because these are internals that can change and have no API stability guarantees, and I don’t want to break users in the future.

In the meantime, a feature request has been filed to Gradle, so, @DanySK, please, put your 👍 on this issue instead: https://github.com/gradle/gradle/issues/13952