Clojurians Log v2
Clojure programming
Channels
Apps
babashka 2026-09-20
jdjohnston 2026-09-20T00:55:56.693709Z
Situation: Offline, working with a locally developed jar installed (with leiningen to ~/.m2/repository . JVM Clojure can resolve the :mvn/version coord, but not babashka. Workaround is to either use local/root or to be sure to use BABASHKA_DEPS_RESOLVER=jvm the first time. Annoying. A weird corner case that may not be worth handling, but I thought it worth mentioning.
✅ 1
borkdude 2026-09-20T06:40:17.178769Z
Can you make a repro with steps? I'll fix
borkdude 2026-09-20T06:44:45.929119Z
Might be relevant which dep it is
borkdude 2026-09-20T07:12:51.319349Z
Is it a normal release version or a SNAPSHOT?
jdjohnston 2026-09-20T09:28:29.014799Z
It's a SNAPSHOT. I'll try making it a release & see if that makes a difference. Pretty sure the issue is that when leiningen installs it, the only metadata is maven-metadata-local.xml . If I do a step-by-step, it will probably be easier to make a github gist. Hopefully sometime in the next day or two.
borkdude 2026-09-20T10:52:14.716809Z
I merged a fix to master. Can be tested with dev build once CI finishes.
borkdude 2026-09-20T10:52:40.663409Z
SNAPSHOT was indeed the differentiating feature
jdjohnston 2026-09-21T00:18:32.778879Z
(All offline) I can confirm both: 1) bb before the fix could resolve local deps with release coords. 2) Latest version can also resolve SNAPSHOT deps . All offline & without any .cpcache . Wow! What a precise set of conditions needed to trigger the problem: offline, locally developed jar, installed to ~/.m2/repository , with SNAPSHOT version
👍 1