I have a couple plot twists here (eg lein with lein-tools-deps for … reasons), and I don’t think I understand classpath/build stuff all that well.

(suppose now that I’ve boiled it down like that I could check it fairly easily)

(doing that)

there is no "by default" under tools.build - either can be done, depends what you're doing

ah ok I was using the uberjar script in the tools.build guide

that script is copying things from resources to the classes dir which is included into the uber jar

so I think the answer is yes, it should be included

my experiment seems to indicate: yes, the nested resources will get yanked in

build-clj makes some assumptions about what's "typical": copy src + resources; compile src. But in general you have complete control.

ok so the problem I’m having with my local/root lib resources not getting rolled up is probably some mismatch weirdness deep in lein-tools-deps and I can work around it by adding "lib/foo/resources" to the :resource-paths in project.clj

(until such time as I can retire lein out of the project entirely)

lein-tools-deps -- there's your problem 🙂

ha well it’s providing a nice stepping stone in the middle of the river

honestly this has been the only rough edge so far

I archived boot-tools-deps because it only worked in the simplest cases and just caused confusion and frustration beyond those -- and I see a lot of the same around lein-tools-deps (although I think lein is slightly more amenable to such surgery).

It's been about six years since I last used lein for anything other than helping beginners with problems... 🤷:skin-tone-2:

ha well, yeah, I started the project in 2015 so that checks out

See https://github.com/seancorfield/build-clj#typical-buildclj-with-build-clj for a version with defaults 🙂

oh right on! Thanks for this and, frankly, all you do.

At work, we build our uberjars like this:

(bb/clean {})
          (b/copy-file {:src version-clj
                        :target "target/classes/ws/uberjar/release.clj"})
          (bb/uber {:main main-class :uber-file jar
                    :compile-opts {:direct-linking true}})

(spit version-clj (str "(ns ws.uberjar.release)"
                           "(def version \"" (git-version) "\")"))

(defn git-version
  "Return a git version string"
  []
  (sh "git" "describe" "--tags" "--match" "b[ui][il]l[di]*"))

I do something similar for the version. The uber task in my build.clj writes out a version.edn in the resources directory which is then read by the config management library (`aero` in this case) on startup.

This is not particularly easy right now

You could exclude it in all of your top level deps, then -Stree I think

Thanks, I didn't know about -Stree

I was always using trace

Oh, hmm, trace is working okay now too. I think I just messed up the exclusion earlier. Sorry about that