Generally no. You could get bytecode and decompile it if suitably desparate

Ok, cool. I'm not that desperate, but thanks for the confirmation. I'll try to see if my gray matter can work as a soft backup

Unfortunately, I don't think you can even get the bytecode once it is loaded.

Fun fact, albeit unhelpful: In Emacs Lisp, functions are their data structures, so there you could have printed them out from memory. I've used this fact to extract the parameter list from the actual function definition for use in auto-generated documentation, as one example of its applicability. 😅

Just to exclude the obvious - does your REPL not have history?

Not for what I need, I was working in an editor and then sending files to the repl via editor integration

I had kind of assumed there was no way to get back to the source, but also last week I pulled in some code via (def f (load-file "foo.clj")) where foo.clj consisted of (fn [x ] ...), and I was surprised to see some actual source code come back when I ran (str f). So I thought maybe there might be a cached version kicking around the REPL or something.

...although now I'm having trouble replicating that behavior. 🤷

Can you use (source function-name) to recover it?

With the CLI, you'd use build.clj and just copy the test folder as well as everything else you copy into the target folder to build the JAR.

See https://clojure.org/guides/tools_build#_compiled_uberjar_application_build :

(b/copy-dir {:src-dirs ["src" "resources"]
               :target-dir class-dir})

(I can't answer the lein aspect -- haven't used it since 2015)

Thanks, really I was wanting to do this in Maven, but I’m thinking at this point to shell out from maven, as I couldn’t find info in this regard.