-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle Kotlin DSL changed method signature of NamedDomainObjectContainerExtensionsKt.invoke #444
Comments
Is there a work around for this? |
A workaround is to rewrite the KtDslCompatibilityUtils.configureNamedDomainObjectContainer and therefore functions that depends on it.
Actually you just have to change configureNamedDomainObjectContainer and id if you are able to build your local protobuf gradle plugin. |
CC @EdGue42 for grpc/grpc-java#8027 |
Gradle has reverted the API deletion at gradle/gradle#15508. Try upgrading Gradle to 6.8 RC3 or later if you are experiencing this issue. We will still try to migrate to Action-based API, but currently we are not able to find newer releases of |
Seems to be solved by #531 |
In KtDslCompatibilityUtils.java the plugin calls
NamedDomainObjectContainerExtensionsKt.invoke(container, block)
withblock
being aFunction1<? super NamedDomainObjectContainerScope<T>, Unit>
. In the latest Gradle build (6.8-milestone-2), that signature has been changed toAction<NamedDomainObjectContainerScope<T>>
: gradle/gradle@593001e, so builds using the Kotlin DSL fail using new builds.The text was updated successfully, but these errors were encountered: