Hey, folks! I face an issue when one adds a repository with

exclusiveContent

filters defined twice – none of the repositories is eventually picked for the dependency resolution. Is that an expected/known issue?

plugins {
    id("java")
}

repositories {
    mavenCentral {
        exclusiveContent {
            forRepositories(this@mavenCentral)
            filter {
                includeGroup("junit")
                includeGroup("org.hamcrest")
            }
        }
    }
    mavenCentral {
        exclusiveContent {
            forRepositories(this@mavenCentral)
            filter {
                includeGroup("junit")
                includeGroup("org.hamcrest")
            }
        }
    }
}

dependencies {
    testImplementation("junit:junit:4.13.2")
}

This fails with:

foo:test: Could not find junit:junit:4.13.2.
Required by:
    project :

You define two separate repositories and configure for both that the dependency is exclusively present there, what do you expect should happen? 😄 That both repositories happen to point to the same URL is irrelevant for this. That could be intended, like one for snapshots, one for releases and each with separate content filters, ...

This is just a simplified example. For performance reasons, I’m providing a custom repository helper to add a more complex Ivy repository with such a filter. By accident, one of the users already called that helper twice, adding the special repository to the project twice and eventually making the resolution fail.

Yeah, but my question stays the same. 🙂

This is technically possible, but I’m surprised with the outcome.

Again, you define two repositories and configure for each that X is exclusively present in that one. My question was sincere, what would you expect to happen?

I’d expect to use both for resolving the given dependency.

But you configured that the dependency is exclusively in that repository

Can we have

notThatExclusiveContent

then? 😉

I mean, you're welcome to open a feature request to change the logic in that way, then see what the Gradle folks say. But then it would not really be exclusive. Maybe it would make sense to actually fail with a meaningful error if something would be exclusively in two repos though. 🤷‍♂️

I want to make sure that one repository won’t be used for searching any other dependencies than requested – as it is supposed to serve just a specific content with fixed group.

The "not that exclusive content" would probably be something like

repositories.configureEach {
    if (this is not_my_special_repo) {
        content { 
            exclude...
        }
    }
}

Oh my, rookie mistake.