2025-07-14 tools-deps | Clojure Slack Archive

tools-deps

2025-07-14T21:07:30.984739Z

for tools deps, is there a way for me to for a project B build the classpath of local project-a passing some aliases?

{:paths ["src"],
 :deps  {org.clojure/clojure "1.11.3"
         ;; Project B depends on Project A's main code
         project-a/project-a {:local/root "../project-a"
                              :aliases [:dev :testing-tools]}}}}

Alex Miller (Clojure team) 2025-07-14T21:07:55.302369Z

currently, no

2025-07-14T21:08:06.735219Z

noo :((

Alex Miller (Clojure team) 2025-07-14T21:08:08.096669Z

but I'm moving towards that

👍🏻 1

2025-07-14T21:08:44.523969Z

because I'm going to teach some QA folks to test the application in a new clojure project

2025-07-14T21:09:07.682409Z

and would be amazing if I export a dev function for them to use in their QA project

2025-07-14T21:09:13.310849Z

:))

Alex Miller (Clojure team) 2025-07-14T21:23:11.520579Z

you could move the tests into a separate project. I know that's not a fun idea.

👍 1

2025-07-14T21:28:17.031029Z

The test tooling at least ok

seancorfield 2025-07-14T22:43:25.076159Z

@alexmiller Any thoughts on this you can share publicly yet? It's been an ask for a long time 🙂

Alex Miller (Clojure team) 2025-07-14T22:44:08.275859Z

Not really, just been busy with other stuff

Alex Miller (Clojure team) 2025-07-14T22:47:46.514299Z

I’m in the process of splitting tools.deps into a subset tools.deps.edn that is focused only on reading/understanding deps.edn (no ties to maven git etc). The goal being to have a low weight lib for tools to consume deps data. Trying to do this before adding new features to deps.edn (of which there are several id like to add)

🙏 1

seancorfield 2025-07-14T22:49:18.880389Z

Ah, nice.

Clojurians Log v2

tools-deps