This message was deleted.
# community-support
s
This message was deleted.
t
Yes, moving from buildSrc to an included build is the natural move forward (and
gradle init
will do just that in the next version)
j
thanks!
just a straight move and includeBuild should do the job?
j
thanks i'll look at that!
t
buildSrc automatically applies the java-gradle-plugin, but if you're already using precompiled plugins then you're already applying another plugin (groovy-gradle-plugin or kotlin-dsl) that itself applies java-gradle-plugin, so it should Just Work™ 1. rename buildSrc to, say, build-logic 2. add includeBuild to the settings.gradle/settings.gradle.kts 3. optional but recommended: make sure the new project itself has a settings script
1
j
thanks! great to know.
i'll be doing that this week.
m
You don't need to publish them. you can use them in local maven also
j
i'd rather just have them as part of the build and not have any publish means.
will my
buildSrc dependencies
be included in the class path for gradle? IE i depend on the kotlin plugin to provide conventions in my precompiled scripts