What will the future of settings plugins be? Should they only be used as ecosystem plugins that does not do anything in the settings phase as

defaults

is possible now? Relatively unrelated to Gradle Declarative, but settings plugins helped to just aggregate all modules into one when you want to aggregate without having to manually put all those

foo(implementation(...))

in that module (Dokka, etc). Would we get some way to "auto aggregate" the relevant modules into one on those cases, or should we keep doing the wire in a settings plugin? If this is the case, some utility function that does the trick easily (and with project isolation support) would be really nice.

AFAIK settings won't go away. But I would never ever expect defaults in a global ecosystem plugin.