clj 1.10.1.469 and tools.deps.alpha 0.7.541 released...

- FIX: exclusions were not canonicalized and could fail to match and exclude
- PERF: cache Maven session and use Maven session cache
- FIX: Remove slf4j-nop as dependency of tools.deps.alpha

if you're a user of tools.deps.alpha, you can now define Maven session boundaries around your use of tools.deps.alpha by wrapping clojure.tools.deps.alpha.util.session/with-session around one or more calls into tda (see https://github.com/clojure/tools.deps.alpha/blob/master/src/main/clojure/clojure/tools/deps/alpha/script/make_classpath.clj#L58 for example)

you may also need to add slf4j-nop as a dep if you were previously relying on getting it via tools.deps.alpha

@alexmiller Under what circumstances might I expect with-session to make a difference?

I just updated clj-new to use the latest t.d.a and wrapped the pair of t.d.a calls in that, but saw pretty much no difference in time spent generating a template (from an empty M2 repository each time).

(session/with-session
    (-> (deps/resolve-deps deps resolve-args)
        (deps/make-classpath (:paths deps) {})
        (str/split (re-pattern java.io.File/pathSeparator))
        (->> (run! pom/add-classpath)))))

It will only help if you’re talking to repos of course

But in particular it makes a difference taking to s3 as it’s slow

For building a large classpath (without cp cache), when talking to s3 it was as much as 50% better

And in other cases, no observable difference

Ah, OK. So it's harmless at worst, and might be helpful for some small class of clj-new users...?