and or just shelling out to system myself

will that work if

gitClone

is part of

build

or will clone always have to be done as it's own step

I think in this case I do

but I'm not sure about that either

We use approach with conditional include a lot as optional way to develop library together with our app

so don’t use gradle to manage repos for you

because main case: clone some library sources, include as a composite builde, change lib, [optional] change app to work with new lib version, commit lib, publish, commit app that uses new version of library

composite build just allow to develop and test library together with app, so it much faster and easy

I was just wondering because you suggested you had the option not to develop the app with the libraries

ok, I'll go on to implementing this, which solves big headache

might convert that build to kotlin too

also, we use this approach to be more flexible: //settings.gradle

if (file('local-settings.gradle').exists()) {
    // You can create file  local-settings.gradle in root dir and
    // add to this file your local modules or composite builds
    apply from: 'local-settings.gradle'
}

local-settings.gradle in .gitignore, so each developer can include any projects just put them to local-settings.gradle and do not worry about modified settings.gradle that should be under vcs control

you also can include some test modules there

honestly I was looking into switching to gradle in part just because I thought composite builds were possible, and that I might be able to do main, test-lib, test

instead of just main, test

maven > gradle > gradle w/ kotlin

ugh can I stop reworking build scripts

lol

btw, do you have any better way of sharing plugin configuration amongst your composite libs, than writing a "plugin bundle"?, or copy and paste

Composite builds completely independent, you cannot share anything

but you can write own plugin that encapsulate that logic for your projects

Also, you can use script plugins, not only binary ones

task("build", {
    dependsOn(gradle.includedBuild("is").task(":build"))
    dependsOn(gradle.includedBuild("sec").task(":build"))
})

so I have that in my build.gradle.kts

and when I have that but a clone hasn't been done

the gitClone is still blowing up

I'm trying to get all of the "sub projects suites" to be run

is there a better way than also protecting it with a conditional?