<@U6GET2VD4> it unfortunately looks like groovy dynamicness - <https://github.com/researchgate/gradl...

# gradle

[mkobit]

@Lucas it unfortunately looks like groovy dynamicness - https://github.com/researchgate/gradle-release/blob/b76fb21cc325f689c154b5674c4c96054cbc6f02/src/main/groovy/net/researchgate/release/ReleaseExtension.groovy#L77-L121

[Lucas]

@mkobit So there is not a workaround, right? Just choosing another plugin that's more Kotlin friendly.

[Czar]

you could create an issue for them or do a PR with needed refactoring, but from the looks of their issue tracker, their development cycle is kinda slow, so YMMV.
Alternatively you could put the plugin configuration in a groovy file and apply it in kts.
If you don't have specific requirement to use it and don't want to have groovy dsl at all, using something more kotlin-friendly would be your best bet.

[mkobit]

the kotlin workaround would be ugly
it might look like (untested)

git {
  methodMissing("git, delegateClosureOf<GitAdapter> {
  }
}

but i dont think configuring the GitAdapter looks nice either because so much of that plugin is built around dynamicness of groovy

you could also probably just put this part in a groovy gradle file and apply it from your kts

[Lucas]

Using the methodMissing doesn't seems to be a solution because the requireBranch property is from a class named GitConfig that's inside GitAdapter. Using a pure Groovy Gradle file worked and it's easier.

Thank you so much @Czar and @mkobit!