-
Notifications
You must be signed in to change notification settings - Fork 412
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
Merge multiproject (composite build) docs #1864
Comments
Yes, it's supported by default, please see http://kotlin.github.io/dokka/1.5/user_guide/gradle/usage/#multi-module-projects |
As for composite builds - as long as you add output of the DokkaPartial tasks from those composite builds to the root DokkaMultiModule task via childDokkaTasks it shouldn't be a problem (we've not tested that one yet though) |
@kamildoleglo note I am asking about multiproject and not multimodule. I am already using |
I will try the |
Sure, but AFAIK you can use the tasks from composite builds like ordinary ones (at least their output and that's what we're after). Worst-case scenario is that you'll have to create a wrapper tasks in the project for the tasks from the composite builds, but I don't think this will be necessary |
I'll close the question as resolved, hopefully you were able to figure it out. In case anyone else has the same question or it's still relevant, please consult Dokka's documentation, it might have answers |
@DanielRibeiroMaciel-TomTom Hi, Daniel. Did you succeed in merging mult project documents? I am struggling with the same issue. |
How do I merge multiproject docs? Is that currently possible? We're using 1.4.30.
If not, is there a workaround? In older versions of dokka it was possible to add external files to the classpath, but It is not clear to me how I could do that in the newer dokka rewrite. Especially if I still want the modules from the composite project to appear as modules in the merged dokka documentation?
It would already help if it was possible to just add the sources of the secondary project to the dokka classpath of the parent project.
The text was updated successfully, but these errors were encountered: