Aaah, I see. Just for the record, how I came to my wrong conclusion:
I deleted the log4j from my maven repository:
rm -rf ~/.m2/repository/org/apache/logging/log4j/
Ran my build:
$ clojure -X:depstar uberjar :jar target/foo.jar
Downloading: org/apache/logging/log4j/log4j-core/2.14.1/log4j-core-2.14.1.pom from central
Downloading: org/apache/logging/log4j/log4j/2.14.1/log4j-2.14.1.pom from central
Downloading: org/apache/logging/logging-parent/3/logging-parent-3.pom from central
Downloading: org/apache/logging/log4j/log4j-api/2.14.1/log4j-api-2.14.1.pom from central
Downloading: org/apache/logging/log4j/log4j-core/2.14.1/log4j-core-2.14.1.jar from central
Downloading: org/apache/logging/log4j/log4j-api/2.14.1/log4j-api-2.14.1.jar from central
...
And wondered why it downloads log4j?
And then I saw the update log4j again commit from Alex in the clojure/tools.logging
https://github.com/clojure/tools.logging/commit/8e8f899c00d79b03a7f5a3a83e52433d689feaf7
, (payed no attention to pom.xml) and missed that it's only in the dev profile of the project.clj, since it's higher up in the file and does not(!) get listed in the additions/deletions listing on github..
And now after being corrected I see that it's the build dependency on depstar in my deps.edn:
:aliases
{:depstar
{:replace-deps
{com.github.seancorfield/depstar {:mvn/version "2.1.303"}}
:ns-default hf.depstar
:exec-args {}}}
which depends on log4j.
Thanks guys for helping me out.
Edit: formatting