Specify the order when a task depends on 2 other tasks

Hi @jendrik thank you for taking the time to reply and explain some things.

I do have those implementations along with a bunch of project dependencies like spring-boot etc.

dependencies {
    implementation project(':shared-code')
    implementation project(':shared-resources')
    implementation project(':frontend')
}

Yet when I specify the task to depend on buildClientSideCode it does not work correctly.

I did solve it for now based on the projects maven setup. I guess for that is currently what we need. Any optimisations are definitely made but we’ll take it one step at a time

I have now the following setup which works perfectly for me right now while I look at the docs you gave me to alter anything

task resolveFrontendCode(type: Copy) {
    into project.buildDir

    into("resources/main/static/js") {
        from "${project.rootDir}/frontend/dist"
        include "**/*.js"
    }

    into("resources/main/static/css/build") {
        include "**/*.css"
        from "${project.rootDir}/shared-resources/src/main/webapp/css/build"
    }

    into("resources/main/static/images") {
        from "${project.rootDir}/shared-resources/src/main/webapp/images"
    }

    // This task depends on the buildClientSide Tasks for both the frontend and shared-resource
    // subprojects. These need to be build before we can copy the build files.
    it.dependsOn ':shared-resources:buildClientSideCode'
    it.dependsOn ':frontend:buildClientSideCode'
}

Thank you very much for that link that looks to be what I need.
The project has some bigger dependency issues that can be optimised further though, but this has helped me to at least get the project completely running under gradle