mention how to install kotlin-gradle-plugin in plugins block
- Dominant language
- Java
- Stars
- 48
- Forks
- 36
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 8
Description
@keturn commented on [Tue Oct 02 2018](https://github.com/gradle-guides/migrating-build-logic-from-groovy-to-kotlin/issues/26)
The guide says
> Use of the `plugins {}` block to declare Gradle plugins significantly improves the editing experience, and is highly recommended. Consider adopting it in your Groovy build scripts before converting them to Kotlin.
so I tried doing that first. Since my project is a Kotlin project, one of the plug-ins I had to use in the `plugins` block is the Kotlin one.
It's not a core plugin in, and though it was `kotlin-gradle-plugin` when I was adding it to my classpath in the buildscript block, that's not the name it goes by in the Gradle plug-ins repo, so I stumbled over that for a while.
It also wasn't clear to me whether, in my multi-project build, that I still needed to `apply` the plugin in my projects (since the `plugins` block is documented as auto-applying them by default), and if so, which name I use there. (is it still `"kotlin"` or is it the longer ID that is used in the plugins block?)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the guide section that recommends the plugins {} block and read its surrounding plugin examples. Document how to declare kotlin-gradle-plugin there, and clarify whether multi-project builds still need apply plus which plugin name to use; the guide is done when these questions are answered for Kotlin projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100