Anyone seen an example in the wild of using Boot with a top level build.boot that calls a subsidiary project build task? Have got a monorepo with a bunch of libraries and apps within and am trying to decide if Boot is a good fit for build tooling for a system laid out like this.

@crimeminister: "subsidiary project build task” you mean like a boot task somewhere else in the project sources?

@crimeminister: I think @juhoteperi wrote something that builds multiple modules/libraries from a single source tree.

@martinklepsch I have a top level directory with distinct library and application projects (along with devops stuff, VM/container creation, etc.), rather than a single Clojure repo with multiple projects nestled within, if that makes sense

Will take a look around in case @juhoteperi has published something, thanks for the tip!

@crimeminister: I don’t really understand what you want to do

@crimeminister: building jars? calling shell scripts? …?

Something analogous to how Bazel works (http://bazel.io)

All of those, and more… 😁

More simply, from a project root, building a project at /foo based on the contents of /foo/build.boot

and a project at /bar based on /bar/build.boot

so that /foo and /bar are effectively standalone projects

That just happened to be nestled in a single containing repo

Of course, am a total Boot n00b, this might not be idiomatic or desirable…

But it could be nice to have a top level /build.boot that knows how to delegate the building of subsystems by calling their own build configs

Anyways, thanks again!

if you put the tasks you use for building your projects into require’able clojure files you can require them in a top-level build.boot file as well as any other build.boot file. I guess it’s a bit more nuanced than that but usually “there is a way”

@crimeminister: there’s also a #C053K90BR channel FYI

Cool, it escaped me that straight forward (:require) might do the trick, was assuming explicit support for that feature was needed. Off to #C053K90BR I go to lurk 🐊