Hello everyone; In my

settings.gradle.kts

I have a lot of `include()`'s. I was thinking of extracting all those includes out, in extension functions. e.g.:

include("demo-1")
include("demo-2")
include("demo-3")
include("feature-a")
include("feature-b")

Could I somehow create an extension function, outside this file, and include all those in there, afterwards only calling

includeDemoModules()
includeFeatureModules()

?

• You can use a legacy script plugin, but as the name suggests you shouldn't, the have quite some quirks and edge-cases • You can write a settings plugin in an included build that you then can use there • You can put the information in something like a CSV or YAML or whatever you prefer and process that information in the settings script if the main goal is not nicety of the setting script but keeping the information outside • ...

But aren't the plugins found in the included-build evaluated & executed after the settings script ?

Plugins are executed when you apply them

So an extension function wouldn't work ? Having an extension on the

Settings

object i mean

Sure you can, if you bring it to the classpath. You can have it in an included build and either apply a plugin from that build (can be a no-op plugin, just to bring it on the classpath), or a manual setting script dependency to bring it to the classpath.

bringing it to the classpaht means adding it to the

settings.gradle.kts

file using

apply(from="path....")

?

If you use "apply from" you use a legacy script plugin, see above

Can you pinpoint me to the new way of adding to the classpath ? I'm not aware of any other method

Imagine the contents of a script as being the body of the

apply

method of the plugin class

I think the no-op is the only solution here; I've tried the others ones and did not work