Kotlin DSL scope based configuration functions are shadowed by existing configuration methods

[eskatos]

Expected Behavior

dependencies.constraints {
    "implementation"("com.google.collections:google-collections") {
        version { rejectAll() }
        because("Google collections is superceded by Guava")
    }
}

to add a dependency constraints on the implementation configuration.

Current Behavior

Doesn't compile with:

* What went wrong:
Script compilation error:

  Line 6:     "implementation"("com.google.collections:google-collections") {
              ^ Expression '"implementation"' of type 'String' cannot be invoked as a function. The function 'invoke()' is not found

1 error

because DependencyHandler.constraints(Action) would shadow a kotlin extension made available to configure via DependencyConstraintHandlerScope.

Workarounds

Don't use string invoke, prefer either the API or delegated properties.

Or explicitely use invoke():

dependencies.constraints.invoke {
    "implementation"("com.google.collections:google-collections") {
        version { rejectAll() }
        because("Google collections is superceded by Guava")
    }
}

Or explicitely resolve the constraints property:

(dependencies.constraints) {
    "implementation"("com.google.collections:google-collections") {
        version { rejectAll() }
        because("Google collections is superceded by Guava")
    }
}

Context

See #710

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[stale]

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.