Aggregating modules doesn't work without manually adding a dependency on all-modules-page-plugin

[aSemy]

Currently in order to create a Dokka publication that aggregates subprojects, it's required to manually add a dependency on all-modules-page-plugin

plugins {
  kotlin("jvm") version "1.7.20" apply false
  id("dev.adamko.dokkatoo") version "0.0.2-SNAPSHOT"
}

dependencies {
  dokkatoo(project(":parentProject:childProjectA"))
  dokkatoo(project(":parentProject:childProjectB"))

  // A dependency on all-modules-page-plugin is required for aggregating subprojects.
  // A version is not required, Dokkatoo will automatically add one.
  dokkatooPluginHtml("org.jetbrains.dokka:all-modules-page-plugin")
}

This dependency should be added automatically.

[hfhbd]

Does this issue also include the adding all modules manually using dependencies { dokkatoo(projects.foo) }? With big projects and adding new modules it is easy to forget to add the new module in the root project too. Would using a BuildService help to register the projects automatically?

[aSemy]

@hfhbd So you want Dokkatoo to automatically set up a multi-module aggregation, if possible? I think that's worth investigating, so please make a new issue. I think it would be possible for Dokkatoo to implement that using default dependencies. Such a feature would be dependent on fixing this issue.

[aSemy]

I've pushed a change #127 that makes adding the dependency slightly easier and less verbose. Dokkatoo will now automatically add a version, so all that's required is:

dependencies {
  dokkatoo(project(":parentProject:childProjectA"))
  dokkatoo(project(":parentProject:childProjectB"))

  // A dependency on all-modules-page-plugin is required at the moment.
  // A version is not required, Dokkatoo will automatically add one.
  dokkatooPluginHtml("org.jetbrains.dokka:all-modules-page-plugin")
}

The version will be set from the version set in the Dokkatoo extension:

// build.gradle.kts

dokkatoo {
  versions {
    jetbrainsDokka.set("1.9.10")
  }
}