Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Hi, and thanks for the issue, this would definitely be a major feature.
Currently I have absolutely no clue where to find some documentation, and feel completely lost.
What should I do while waiting for this issue to be resolved ? There must be something I'm missing if Kotlin support is now the "default" for Gradle, there must a documentation somewhere ?
Back to Groovy in the meantime, at least I'm following this issue and will be updated :)
Thanks a lot for your work ! Hope there are simple answers to my questions. Thanks.
About your first question, when importing the project into IDEA point it to the
After that, with proper IDEA support, code assistance should aid you in answering your second question, inside the
For clarification, as mentioned in the Gradle 3.0 Release Announcement:
Thanks for your comments!
I would like to see clear documentation on what the Kotlin specific idioms for writing plugins should be. One of the things that was missing in the early Gradle with Groovy documentation was clear guidance on preferred form, format and structure for plugins. In the early days you couldn't really create useful plugins without using undocumented features and API which were constantly changing. As a result the ecosystem has many wildly varying approaches to writing plugins and existing plugins haves supportability issues.
With Kotlin based plugins and a more mature Gradle infrastructure it would be great to provide templates and examples of the "preferred" plugin architecture and Kotlin coding style. This way people can be guided into a pit of success rather than wandering around in the dark undocumented forest.
referenced this issue
Oct 19, 2017
Do you have any ETA for documentation on Kotlin DSL?
We need at least a few tips on how to translate from Groovy DSL to Kotlin DSL.
As it stands, it's almost impossible for a noob like me to use KTS (as much as I would like to), since:
In my opinion, this should be considered as more important than probably any other feature (except critical bugs), since it prevents early adoption, and thus early feedback.
I basically gained all of my knowledge by reading the various samples that exist and pegging questions into the Gradle chat in the Kotlin Slack. Come by! Say hi!
I agree that there needs to be documentation added.
Perhaps @eriwen could provide some insight into the timelines on that?
I can say that Kotlin DSL 1.0 will not happen without an extensive amount of documentation to help users adopt it. Failing to provide this would be the fastest way to kill such a tremendous launch, and we will delay 1.0 until we have at least:
I think the biggest reason this has not happened yet is that we are optimizing for soonest Kotlin DSL 1.0, and we want to avoid the overhead of changing documentation in the face of breaking DSL changes. I think I and the @gradle/kotlin-dsl team do owe you folks some kind of timeline soon, and I think we ought to meet about it ASAP.