Explain how to mix Groovy/Kotlin project scripts when not using the default script names
- Dominant language
- Java
- Stars
- 48
- Forks
- 36
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 8
Description
@eskatos commented on [Fri Aug 10 2018](https://github.com/gradle-guides/migrating-build-logic-from-groovy-to-kotlin/issues/19)
without hitting the disk in the settings file.
Good
https://github.com/gradle/gradle/blob/dd3e28584484fe44ca19f9d25b794d464aef800c/settings.gradle.kts#L110-L184
Bad
https://github.com/gradle/dotcom/blob/5aa75173ff84d13d597761c64ce1de87b296e0a8/settings.gradle.kts#L87
Contributor guide
No contributing guide indexed for this repository
Research direction
Compare the referenced settings.gradle.kts examples in the Gradle and Gradle Dotcom repositories, focusing on how they mix Groovy and Kotlin project scripts without the default script names. Document the supported approach and explain the distinction between the “Good” and “Bad” examples; the issue is done when this guidance is clear to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100