Another use-case for ProviderExternalModuleDependency support: https://github.com/gradle/gradle/issues/37814

interface DependenciesExtension : Dependencies {
  val api: DependencyCollector
  val implementation: DependencyCollector

  val myLibVersion: Property<String> // has a convention value

  fun libA(): Provider<ExternalModuleDependency> {
    return myLibVersion.map { dependencyFactory.create("org.example.foo:bar:$it") }
  }
  fun libB(): Provider<ExternalModuleDependency> {
    return myLibVersion.map { dependencyFactory.create("org.example.foo:baz:$it") }
  }
}

What enum are you referring to?

I am missing the point, can you clarify?

The current design (due to the missing Gradle feature) is:

serialization {
  version = "1.11.0"
  formats = listOf("json", "cbor") // what configuration is the target?
}

I would prefer:

dependencies {
  serialization {
    version = "1.11.0"
  }
  implementation(serialization.json)
  compileOnly(serialization.cbor)
}

I think it is a bit overkill the need of that explicit version over using the old way and/or including a BOM.

dependencies {
  implementation(libs.serialization.json)
  compileOnly(libs.serialization.cbor)
}

version has a default value

I don't know how the ecosystem will reply, but in my case I am pretty sure I will specify a version + getting instant updates with Renovate.

Well, that's true, but having an included "version catalog" is also nice

On another hand, probably updating the gradle plugin will update that default version too, so it can be redundant. What I would prefer is to have a standard, because Kotlin can have this behavior, other languages or libraries do not, and can be a bit annoying over the other one that just work in any case because it just uses the versioning + dependency resolution system Gradle uses.