How to flatten modules for multi-module configuration?

[Zeliret]

Question
Hi there, I was able to successfully generate documentation for my multi-module project. The project is SDK, so basically a set of libraries with the same root package names.

Is it possible to flatten this structure and display packages instead of the modules?

So basically if I have:

Module A:
my.cool.package.a

Module B:
my.cool.package.b

Can I get instead of:

Module A
-- my.cool.package.b
---- some class... 
Module B
-- my.cool.package.b
---- some class...

this:

my.cool.package.a
-- some class... 
my.cool.package.b
-- some class...

etc...

[whyoleg]

Hey!
Overall, in current Dokka Gradle plugin we do have collector tasks for this, though the initial use-case for this was to support multi-module javadoc.
Anyway, in Dokka Gradle plugin v2 we are going to drop out-of-the-box support for collector tasks.

Is there any reason why you can't use multi-module output? Or you distributing it as a single jar/klib?

[Zeliret]

Hey! Overall, in current Dokka Gradle plugin we do have collector tasks for this, though the initial use-case for this was to support multi-module javadoc. Anyway, in Dokka Gradle plugin v2 we are going to drop out-of-the-box support for collector tasks.

Is there any reason why you can't use multi-module output? Or you distributing it as a single jar/klib?

For now we are using the default multi-module output, but I was thinking about merging it because from the perspective of the consumer there is no need in knowing what module contains the classes, most of them are transitive dependencies.