Using JVM packages for precompiled script plugins, rather that . in the file name.

[yogurtearl]

Currently this repo uses . in the file name of precompiled script plugins.

i.e. a file at src/main/kotlin/com.example.repositories.settings.gradle.kts

can applied with:

plugins {
    id("com.example.repositories")
}

Like this:

But this alternative using JVM packages accomplishes the same thing:
The below can also be applied with:

plugins {
    id("com.example.repositories")
}

I tend to prefer the second one because it matches the pattern of normal kotlin source code.

Is there a reason that using . in the file name rather than JVM packages is seen a more idiomatic?

Also, maybe consider turning on the Github Discussions feature on this repo, for items like this. :)

[jjohannes]

I think both options are fine and I don't really prefer one over the other.

The reason why I use the one without package in all examples is that the package is not supported in the Groovy DSL. Many users use that for various reasons and I prefer to have setups that work with both DSLs similarly.

[jjohannes]

Also, maybe consider turning on the Github Discussions feature on this repo, for items like this. :)

I have to think about this. I am reluctant to open even more communication channels...

Please continue to post any question/discussion as issues here. I think I'll add a kind of FAQ section to the Readme and then link question/discussion issues from there.