-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation is not generated on 1.8.20 with KMP Multimodule project #3107
Comments
Would you be able to tell us what exact problem you're running into? Maybe a stacktrace or a description of what is happening? In case it's a new problem that we haven't encountered yet. |
I already described my problem in the issue description. The documentation is not generated. No stacktraces are produced The console prints the tasks as if they were executed. |
This also applies to the html documentation |
I've cloned the project locally, commented out the scary Dokka configuration blocks, and run Is there any reason you're configuring |
Yes, because of #2977 I'm puzzled about the fact that you were able to build the project without running into that issue. Anything else you changed? |
Dokka 1.9.0 has been released, and it includes some workarounds for this problem. See the following issue for details: To avoid the spread of information and have updates in a single place, I'll close this issue and a few others as duplicates in favour of #3153. |
Describe the bug
The documentation is not generated despite the task completing successfully with Kotlin 1.9, Dokka 1.8.20 and a KMP project
Expected behaviour
The documentation is generated or the task fails explaining what went wrong
Screenshots
You can visit the javadocs site to see how it looks:
https://opensource.respawn.pro/FlowMVI/javadocs/index
To Reproduce
See the project https://github.com/respawn-app/FlowMVI
Dokka configuration
Configuration of dokka used to reproduce the bug
Installation
Are you willing to provide a PR?
I don't know what's wrong to provide a PR
The text was updated successfully, but these errors were encountered: