neil add build also generates a standard build.clj file in an existing project (and adds the deps in a :build alias if it doesn't exist yet), including deps-deploy which is lazily loaded. If you have any suggestions for that generated build.clj feel free to make those! The version is retrieved from :aliases :neil :project :version if it's there, which gives a bit more declarative info in the deps.edn. If deps.edn had a widely adapted convention for this, I'd use that. :name is in there too for the library name.

So if we’re using build-clj what should we do? Copy source of functions we were calling into each build.clj?

Per build-clj's README: I would strongly advise you learn to use raw tools.build instead for anything beyond the simplest build script needs!

You don't want to copy the build-clj functions -- they are far more complex than you will need for any build.

The readme links to https://clojure.org/guides/tools_build which has "raw tools.build" examples for library and application JARs.

We have stopped using build-clj at work and as soon as I've removed it from the deps-new templates, I'll likely archive the repo.

Got it, thanks 🙏