This message was deleted.

the Configurations are created here: https://github.com/adamko-dev/dokkatoo/blob/2e9fde349bfc5a0933d2758e9be137e08fbb3957/modules/dokkatoo-plugin/src/main/kotlin/formats/DokkatooFormatPlugin.kt#L204-L361 If I have 3 subprojects:

Root project 'dokkatoo-example'
   +--- Project ':childA'
   +--- Project ':childB'
   \--- Project ':docs'   (depends on :childA and :childB)

Each subproject needs to provide the following files: •

./build/dokka-module/<format>/...

- a module directory •

<format>-module-descriptor.json

- a single configuration file • Dokka Plugins classpath - JAR files were used to build the subproject’s

dokka-module/<format>

I’ve created a Configuration (resolvable=false,consumed=true) for each of the above. And then

:docs

has resolvable Configurations in order to execute the Dokka Generator task • all `dokka-module/<format>`s from other subprojects • all

<format>-module-descriptor.json

files from other subprojects • Dokka Plugins classpath • Dokka Plugins, without transitive dependencies • Dokka Generator classpath (which is Dokka Plugins + Dokka Generator) All of these extendFrom() a base

dokkatoo

Configuration, so actually in the build script it’s succinct.

plugins {
  id("dev.adamko.dokkatoo")
}

dependencies {
  dokkatoo(projects(":childA"))
  dokkatoo(projects(":childB"))
}

However, every Configuration is specific per format. There are 4 output formats at the moment (HTML, Javadoc, Jekyll, Markdown), so there are 4 times as many incoming and outgoing Configurations.

You could maybe have one configuration and then work with the artifact type to get the artifacts you need currently. But just guessing here, didn't try that yet.

hmmm maybe, but I’m wary about using artifactType because it’s not well documented and I’d be concerned that it might interfere with selecting JARs

I'm not sure whether artifact view is not too late to change the attributes. Maybe the artifact attributes like attribute type, yes.