Feedback welcome We have a new `dev` build availab...

# dokka

[Sebastian Sellmair [JB]]

Feedback welcome
We have a new dev build available that we would be very happy to get feedback for 🎉
_Build_: 1.4.0-dev-35

_____
Gist of changes:

1. Gradle Plugin
Our Gradle Plugin had some very hard to fix issues and we put a lot of effort into
• Reducing complexity of its implementation
• Fixing internal issues e.g. (bad UP-TO-DATE) behaviour,...
• Fixing UX issues like "re-declaring source sets for mulitplatform projects", replacing paths with java.io.File, using Gradles Property/Provider APIs etc...
We hope that "just applying the dokka plugin" is all that most build authors need. The plugin can be seen as companion to the Kotlin Gradle Plugin.
See the pull-request for further details: Simplify Gradle Plugin
Feel free to drop me dm's if you need any help migrating or experience any issues!

2. Merging visible source sets
Issue: DokkaCollectorTask: Merge source set bubbles
This was noticed while running the collector task on larger projects like the Spring framework.
Source sets with the same displayName and platform will now be represented as one in the frontend. We hope that this unblocks some of you that rely on the collector task.

3. Updated compiler to 1.4.0

4. A lot of smaller bugfixes
Further details are available in our milestones:
• 1.4.0
• Stable
__

Some comment on version numbers
You already noticed, that we aligned our version number to the compiler version we bundle. (e.g. 1.4.0, 1.4.0-rc, ...).
There were some minor hick-ups when we changed to this numbering schema, but I would like to clarify some things.
Dokka 1.4.* is not a stable project. It is still considered alpha!
For now, we agreed on using the following naming schema
• `{comiler-version}-dev-{build-number}`: for preview builds
• {compiler-verison} for releases and pre-releases (no dokka maturity included)
• {compiler-version}-{patch number} for patch releases
__

Some comment on kotlin-dev
This will probably be the last build we push to the kotlin-dev repository. We will migrate dev builds to space packages in the near future.

[Lukas K-G]

Sorry if that is a stupid question, what repo do I have to include to get this running? Is there some documentation I am missing? 🤔

[Sebastian Sellmair [JB]]

maven(url = "<https://dl.bintray.com/kotlin/kotlin-dev>") ☺️
Not a stupid question, I have to look it up also every time! 👍

[Zach Klippenstein (he/him) [MOD]]

What does migrating to space packages mean for consumers? Is there a different maven repo we'll need to use? I assume it doesn't mean we have to be using space to use Dokka.

[Sebastian Sellmair [JB]]

Oh yes, it just means that there will be a different public repository for -dev builds ☺️

[Rachel]

Thanks!! I think the current README file cannot be updated until releasing another version. Could some README details be located into another file to be updated with these DEV versions? I cannot make Gradle configuration work now 😅 Just getting `Could not create domain object 'main' (GradleDokkaSourceSetBuilder)`Thanks in advance!

[Sebastian Sellmair [JB]]

Hey Rachel, this is a good idea of yours! ☺️
May I offer my help in migrating, just drop me a DM ☺️

But tip: ./gradlew --stacktrace : Will mostly show you that your groovy does not compile and where. Best guess: someConfiguration = some param needs to be replaced with someConfiguration.set(some param

Pro tip: Use kotlin dsl build scripts, because groovy [...] 😁

[Rachel]

I imagine the content of [...] 😂 Thank you so much @Sebastian Sellmair [JB] , I'll try it!!

[Sebastian Sellmair [JB]]

Hihi, no one will ever know what I censored here 🤷
If you encounter any further issues, please let me know here ☺️