Clojure Q&A - Recent activity in Tools

Answer selected: gitlibs/tags throws a NPE if the repository has no tags

Sun, 24 May 2026 22:06:48 +0000

Thanks! Fixed in tools.gitlibs 2.6.217.

Comment edited: shasum not found error when using ./posix-install on linux

Thu, 12 Mar 2026 00:09:15 +0000

from https://clojure.org/guides/install_clojure

> This installer should work on Linux, BSD, and even Mac (but will conflict with brew!)

That made me think that I should expect the posix installer to work.

Closed: TDEPS-269: checksums should use sha256sum instead of shasum

Tue, 27 Jan 2026 15:31:37 +0000

This commit broke our Docker build: https://github.com/clojure/brew-install/commit/d6d540756cb0a6342374db529d07f1de35d5bc71

because shasum is a perl executable provided on Fedora by perl-Digest-SHA-1 rpm, but it's not available on the UBI platform. The standard way to validate checksums is through sha256sum provided by coreutils on most (if not all) linux distributions.

The jira ticket even talks about sha256sum, but then the commit doesn't use it: https://clojure.atlassian.net/jira/software/c/projects/TDEPS/issues?jql=project = TDEPS ORDER BY created DESC&selectedIssue=TDEPS-269

Commented: How do you use a private maven repository with deps.edn

Tue, 27 May 2025 18:18:13 +0000

Moved again, under "Maven authenticated repos" at https://clojure.org/reference/clojure_cli#procurer_mvn

Commented: Add support for BOM (Bill Of Materials) dependencies

Sat, 08 Mar 2025 15:20:31 +0000

At $WORK we've been asked to support some azure services and their libraries are packed together into a BOM: https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/boms/azure-sdk-bom/README.md#adding-the-bom-to-your-project

Would the linked approach also handle the situation where sub-packages wouldn't require version specification? (it's mentioned in the next paragraph in the link to the azure sdk above)

Closed: Clojure cli on windows relies on MD5 which is not FIPS compliant

Fri, 19 Jul 2024 17:34:16 +0000

It looks like the default powershell module uses the MD5 crypto service provider to compute a hash for the cached classpath file (I think);

function Get-StringHash(str)  {
    $md5  = new-Object -TypeName System.Security.Cryptography.MD5CryptoServiceProvider
...

Under certain installations of Windows with FIPS mandated (e.g. by the system admin), MD5 is simply disallowed and clj will fail with an error regarding FIPS in this function.

A simple alternative is to change to a compliant algorithm, e.g. SHA1,

function Get-StringHash(str)  {
    $md5  = new-Object -TypeName System.Security.Cryptography.SHA1CryptoServiceProvider
...

This should not have an effect on the operation of the clojure cli script, other than changing the actual hashed value of the classpath, which should be internally consistent with the script's prior runs. Unless something depends on the exact MD5 hash of the cpcache (it doesn't look like it), this should be a quick fix for cases where FIPS is forced.

Commented: Clojure CLI: --report incompatible with -X ?

Tue, 17 Jan 2023 14:14:56 +0000

Things have changed in the implementation here a number of times. In current versions, -X/-T will go through clojure.main to exec functions. I would currently consider that an implementation detail (but probably one that will stick). We have a jira to consider this more fully at https://clojure.atlassian.net/browse/TDEPS-193

Retagged: Set GITLIBS in deps.edn

Thu, 01 Dec 2022 15:32:56 +0000

Currently, git libs are cloned to ~/.gitlibs by default, and this can be changed with the environment variable GITLIBS. (See docs)

It would be helpful if I could set that location via an entry in the repo's deps.edn file, akin to :mvn/local-repo:

{:mvn/local-repo "local-m2" :gitlibs "gitlibs" :deps {...}}}

If this could be done, I would also appreciate it being available within an alias. This probably would require implementing the same for :mvn/local-rep first (see relevant Ask).

Answered: Datomic Pro on-prem fails on M1 Mac

Mon, 21 Nov 2022 00:30:31 +0000

Probably better to post this on https://ask.datomic.com so the folks there will see it.

Reshown: Support `:mvn/repos` inside an alias

Tue, 08 Nov 2022 19:25:08 +0000

This is similar to https://ask.clojure.org/index.php/11711/set-mvn-local-repo-via-alias, sorry if I should have just added a note there instead of opening another question.

:mvn/repos does not seem to work inside of an alias either -- only at the top level of deps.edn. If this is intentional, it would be a nicer experience if CLI logged some sort of ":mvn/repos is not supported inside of aliases" warning on launch.

Commented: :deps manifest dependencies do not respect :mvn/repos in dependent project

Tue, 08 Nov 2022 19:02:40 +0000

Maybe this could be an option for each individual dep, since there are some legitimate use cases where you want it.

I'll give you a concrete example:

In Metabase we have our Amazon Redshift extension as a separate `:local/root` subproject; Amazon has its own repo for the Redshift JDBC driver. Ideally we'd just have the custom `:mvn/repos` in the subproject and be able to pull that into the main project whenever we include it. As it is right now we have to copy the repo path and specify `:mvn/repos` in two places.

Something like

```
{:extra-deps
{metabase/redshift {:local/root "modules/drivers/redshift", :mvn/include-repos true}}}
```

would work I think

Edited: Convention for bypassing EDN parsing in -X usage to reduce using quotes in arguments passed from shell

Sat, 08 Oct 2022 18:28:57 +0000

Sometimes quoting strings or shell invocations can be a bit verbose or clumsy in the shell when passing arguments to exec functions (-X) because those arguments have to be quoted with an extra layer since they are parsed as EDN.

This example was recently posted in Slack:

clojure -X:bench :json "$(my_json_producing_cmd --blah)"

and it turned out nearly impossible to pass the JSON as an argument.

Having a way to bypass EDN parsing for such arguments could alleviate that problem.

One possible convention could be to use a leading character which would otherwise be invalid in EDN, such as the / sign:

clojure -X:bench :json /"$(my_json_producing_cmd --blah)"

Alternative approaches:

Use metadata on the function to opt out of processing: that would change the parsing behavior at the implementation side, e.g.:
```
  (defn foo
    {:tools.deps/exec-skip-edn-read #{:a}} 
    [{:keys [a b c]}]
      ...) 
```
Add something to deps.edn config in :exec-args: that would only change the behavior for consumers

Extra things to consider:

The convention should play well with both bash, cmd.exe and Powershell and not mean anything special in the syntax of those shells. I tried / in these shells and this does not seem to interfere.

After experimentation I found that / might work better than @ since @ has a special meaning in powershell:

bb -e "*command-line-args*" /foo @bar
("/foo")

Also @ often means: slurp contents from file and inline that content as arg.

Edited: Calva project type: shadow-cljs vs deps.edn + shadow-cljs?

Sun, 22 May 2022 04:32:03 +0000

Hi everyone, I’ve gone through the shadow-cljs quickstart guide in the GitHub repo README and got the desired message in the browser console. Next, I wanted to introduce deps.edn to the project. I had some (self-inflicted) difficulty in jacking in after adding deps.edn.

System details:
OS: WSL2
Java version: OpenJDK 11.0.15
Clojure CLI version: 1.11.1.1113

With only shadow-cljs.edn in the project, said file contents are:

;; shadow-cljs.edn
{:source-paths ["src/dev"
                "src/main"
                "src/test"]
 :dependencies []
 
 :dev-http {8080 "public"}
 :builds {:frontend {:target :browser
                     :modules {:main {:init-fn acme.frontend.app/init}}}}}

At this point, jacking in with Calva using the “shadow-cljs” project type, which both starts and connects to the “:frontend” build, works like a charm.

As mentioned in the first paragraph, I had difficulty with introducing deps.edn to the project.

Add deps.edn to the main project directory with the following contents:

;; deps.edn
{:paths ["src/main"
"src/dev"
"src/test"]

 :aliases
 {:cljs {:extra-deps {thheller/shadow-cljs {:mvn/version "2.19.0"}}}}}

Change shadow-cljs.edn to:

 ;; shadow-cljs.edn
    
 {:deps {:aliases [:cljs]}
        
:dev-http {8080 "public"}
        
:builds {:frontend {:target :browser
:modules {:main {:init-fn acme.frontend.app/init}}}}}

Jacking in with Calva using the “deps.edn + shadow-cljs” project type at this point leads to an error containing “Failed starting cljs repl for build: :frontend. Is the build running and connected?”

The Calva Connection Log also provides information, including: “shadow-cljs has not been started yet!” and “If you have a shadow-cljs server or watch running then you are not connected to that process.”

The build doesn’t seem to have been started. What if we run npx shadow-cljs watch frontend and then tried connecting to the REPL? Same error messages as before.

It turns out I should’ve instead kept using the “shadow-cljs” project type (in which case the addition of deps.edn goes down without a hitch).

This leads me to wonder:

When to use which project type?
Which is preferred for a fullstack
project?

Thanks to Peter and contributors for Calva!

Commented: Error Building classpath

Tue, 19 Apr 2022 22:09:55 +0000

I have bad news: I still see this with Clojure CLI version 1.11.1.1105:

```
Error building classpath. class java.util.HashMap$Node cannot be cast to class java.util.HashMap$TreeNode (java.util.HashMap$Node and java.util.HashMap$TreeNode are in module java.base of loader 'bootstrap')
java.lang.ClassCastException: class java.util.HashMap$Node cannot be cast to class java.util.HashMap$TreeNode (java.util.HashMap$Node and java.util.HashMap$TreeNode are in module java.base of loader 'bootstrap')
at java.base/java.util.HashMap$TreeNode.moveRootToFront(HashMap.java:1900)
at java.base/java.util.HashMap$TreeNode.treeify(HashMap.java:2016)
at java.base/java.util.HashMap.treeifyBin(HashMap.java:768)
at java.base/java.util.HashMap.putVal(HashMap.java:640)
at java.base/java.util.HashMap.put(HashMap.java:608)
at java.base/java.util.HashSet.add(HashSet.java:220)
at org.apache.maven.model.validation.DefaultModelValidator.validateId(DefaultModelValidator.java:848)
at org.apache.maven.model.validation.DefaultModelValidator.validateEffectiveDependency(DefaultModelValidator.java:660)
at org.apache.maven.model.validation.DefaultModelValidator.validateEffectiveDependencies(DefaultModelValidator.java:584)
at org.apache.maven.model.validation.DefaultModelValidator.validateEffectiveModel(DefaultModelValidator.java:374)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:501)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:437)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:252)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:297)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:175)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:255)
at clojure.tools.deps.alpha.extensions.maven$read_descriptor.invokeStatic(maven.clj:115)
at clojure.tools.deps.alpha.extensions.maven$fn__1128.invokeStatic(maven.clj:143)
at clojure.tools.deps.alpha.extensions.maven$fn__1128.invoke(maven.clj:143)
at clojure.lang.MultiFn.invoke(MultiFn.java:244)
at clojure.tools.deps.alpha$expand_deps$children_task__771$fn__773$fn__774.invoke(alpha.clj:405)
at clojure.tools.deps.alpha.util.concurrent$submit_task$task__479.invoke(concurrent.clj:35)
at clojure.lang.AFn.call(AFn.java:18)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
```

Answered: How can we make it easier for beginners to install Clojure?

Sun, 17 Apr 2022 21:18:05 +0000

"Easier for beginners to install" is complected! Let's split it up.

"Easier for beginners" means not having to use administrative privileges; not having to make a commitment or risk a complicated outcome if an installer does something unexpected; files obviously partitioned (e.g., inside 1 directory) for clarity of erasing it and trying it again and again.

"Easier to install", on the other hand, is not only a tougher problem, but also perhaps a bit secondary. By the time someone is thrilled with the trial, and let us remember that these are top-1% people, they will know whether they even need "installation", and if they do need it, they will be pleased to be given no more of a red carpet than is in the nature of the task.

Leiningen sets a pretty good example (it's hard to beat "download lein" and "./lein") with not even the option of system-wide installation it avoids complications. Nonetheless, Clojure's official getting-started page is not a super place to suggest Leiningen. Lein's deep Maven consanguinity has been a great booster rocket, but a future of direct source-code-repo connections, free of a packaging step or a middleman brokering jars, is closer to Clojure's spirit.

Commented: How can I return data from clojure.tools.cli.api/tree?

Fri, 08 Apr 2022 16:50:59 +0000

I extracted out a new function to calculate the trace in clojure.tools.deps.alpha.tree/calc-trace that can be combined with the existing ctda.tree/trace->tree to get the data. Will be in next release.

Recategorized: Set mvn/local-repo via alias

Mon, 04 Apr 2022 17:23:36 +0000

Having to set local repos a top level attribute or via the command line results in pretty messy CI scripts where every call to clojure needs the added options of -Sdeps '{:mvn/local-repo "..."}'.
This is both noisy and fragile. Moreover, with most CI systems being configured in yml, this can result in a mess of quotes.
It would be preferable to have a :ci alias where mvn/local-rep and GITLIBS could be overwritten.

Thanks
Ben

Answer edited: All kinds of problems trying to run my first Clojure program

Wed, 23 Mar 2022 16:40:14 +0000

Using the clj command line, if I just copy/paste what you have into the repl:

PS C:\Users\joinr> clj
Clojure 1.10.2
user=> (ns clojure-noob.core
         (:gen-class))

(defn -main
  "I don't do a whole lot...yet."
  [& args]
  (println "Hello, World!"))

(defn train
  []
  nil

#'clojure-noob.core/-main
#'clojure-noob.core/train

and then I evaluate (train) and (main):

clojure-noob.core=> (train)
Choo choo!
nil

clojure-noob.core=> (-main)
Hello, World!
nil

Everything seems fine. What are you doing differently?

[ed] I noticed you are following CFTBT. Is this your first time with emacs? If so, a simpler editor/setup may be better, so that you are not learning both clojure and emacs at the same time....(I say this as an emacs user, specifically spacemacs with the default clojure layer and minimal customization....).

Commented: EMacs standard configuration error

Thu, 17 Mar 2022 22:21:29 +0000

As long as you can type code in the REPL and get it evaluated then it shouldn't matter if the window split is vertical or horizontal, that's just how emacs decided to layout its windows. If you want to have them side by side try with "Control-x 0 Control-x 3".

Just to be clear, emacs has nothing to do with Clojure, it just so happens that the Clojure community early on embraced emacs as one of its preferred editors due to its lisp support. There are other editors and IDEs that might feel more familiar to you if you don't want to learn both at the same time and support Clojure via plugins: Visual Studio Code has Calva, IntelliJ has Cursive, etc. I'm not trying to discourage you from learning emacs, it's a fantastic tool if you can invest in learning it, but it can be a daunting task to learn both emacs and Clojure at the same time.

Answered: Allow configuring behavior for -X when it's invoked as entry point

Mon, 28 Feb 2022 22:56:50 +0000

Why not just make a -X entry point function that wraps a simpler function?

Closed: Support --help for tools / use "standard" cli options for clojure tooling

Fri, 18 Feb 2022 14:35:10 +0000

Hello,

Is there a way to get help for a tool other than knowing in advance what it does?
Can we have a standardized --help option ?

Context:

I found out about clj -Ttools list command in an announcement.
Is there a way to see what other things are available besides "list" operations ?
Is there a way to print docs for those ?
Most CLI tools offer a --help or a man page.
I tried some of the things I know from usual OS commands:
clj -Ttools
No function found on command line or in :exec-fn
clj -Ttools help
Function not found: clojure.tools.tools.api/help
clj -Ttools --help
Function not found: clojure.tools.tools.api/--help
This works but for clj, not for the tools.
clj --help

I would argue that clojure should adopt a more familiar CLI interface so people comming into clojure can find their way around.

Of course more advance clojure users could argue that things are good enough as they are - but I don't think there is any standardization on this front.
This leads to having to remember syntax for lots of tools.

I think having a standardized help would improve this a lot:
There are some guides online - first search brought me this https://clig.dev/#help .
I'm sure there are others.

Original discussion on Cojurians slack

https://clojurians.slack.com/archives/C06MAR553/p1635321226061200?thread_ts=1635283780.057200&cid=C06MAR553 .

Answered: tools.build/javac does not handle modules-info

Tue, 11 Jan 2022 14:42:32 +0000

Logged as https://clojure.atlassian.net/browse/TBUILD-25

Commented: clojure -X misreports error if FileNotFoundException is thrown

Thu, 28 Oct 2021 19:33:41 +0000

Thanks. I ran into a similar issue just over a week ago and I've been meaning to add an "ask" about it!

Answer selected: Make tools help more discoverable

Wed, 27 Oct 2021 20:14:15 +0000

Logged as https://clojure.atlassian.net/browse/TDEPS-211

Comment edited: tools.build: are "standard" build tasks under consideration?

Mon, 18 Oct 2021 17:28:33 +0000

Yeah I’m using build-clj. In fact it contributed to this line of thinking.

[edit] and just to add some nuance, while build-clj provides standard _implementations_ of common build tasks, it doesn't say anything about standard _interfaces_ to those build tasks (the latter being the focus of my question)

Datomic ion push fails

Wed, 29 Sep 2021 07:41:53 +0000

Anyone recognize this error "data did not conform" when trying to make a datomic ion push? I am using a windows machine and get the following message:

{:command-failed
"{:op :push :uname my-test-name :creds-profile my-creds-profile :region my-region}",
:causes
({:message "Data did not conform",
:class ExceptionInfo,
:data
#:clojure.spec.alpha{:problems

                    ({:path [:local :home],
                      :pred clojure.core/string?,
                      :val nil,
                      :via
                      [:cognitect.s3-libs.specs/local
                       :cognitect.s3-libs.specs/home],
                      :in [:local :home]}),
                    :spec
                    #object[clojure.spec.alpha$map_spec_impl$reify__1997 0x668a32a4 "clojure.spec.alpha$map_spec_impl$reify__1997@668a32a4"],
                    :value
                    {:description
                     "Unreproducible deployment (no git commit)",
                     :query-group nil,
                     :app-name "app-name",
                     :creds-profile my-creds-profile,
                     :op :push,
                     :uname my-test-name,
                     :allow [],
                     :region my-region,
                     :lambdas
                     {:api-handler
                      {:fn com.anon.app-name.ions.core/api-ion,
                       :integration :api-gateway/proxy,
                       :description
                       "Handles requests to REST API.",
                       :timeout-secs 29,
                       :concurrency-limit :none},
                      :file-upload-handler
                      {:fn
                       com.anon.app-name.ions.core/file-upload-handler,
                       :description
                       "Handles notifications received from S3 when a user uploads a file to uploads bucket.",
                       :timeout-secs 900,
                       :concurrency-limit :none},
                      :file-cleanup-handler
                      {:fn
                       com.anon.app-name.ions.core/file-cleanup-handler,
                       :description
                       "Cleanups orphan files in database. Triggered by AWS Events every midnight.",
                       :timeout-secs 300,
                       :concurrency-limit 1},
                      :common-connector
                      {:fn
                       com.anon.app-name.ions.core/common-connector,
                       :description
                       "Handles common connection tasks between datomic and other Amazon services when required.",
                       :timeout-secs 300,
                       :concurrency-limit :none},
                      :first-platform-connector
                      {:fn
                       com.anon.app-name.ions.core/first-platform-connector,
                       :description
                       "Handles first-platform related connection tasks between datomic and other Amazon services when required.",
                       :timeout-secs 300,
                       :concurrency-limit :none},
                      :second-platform-connector
                      {:fn
                       com.anon.app-name.ions.core/second-platform-connector,
                       :description
                       "Handles second-platform related connection tasks between datomic and other Amazon services when required.",
                       :timeout-secs 300,
                       :concurrency-limit :none}},
                     :datomic.ion.dev.config/resource
                     "datomic/ion-config.edn",
                     :local {:home nil},
                     :bucket
                     "datomic-code-hash"}}})}

Commented: tools.build.api/write-pom does not expose generated pom's filename

Sat, 25 Sep 2021 18:24:48 +0000

For Alex: Thanks!
For Sean: I noticed that update landed in build.clj. I've been using (and loving) it. Thanks to you too!

Answer selected: Do I have to switch to Java 8 or 11 from 16.0.1?

Tue, 14 Sep 2021 21:48:59 +0000

clojure.org does NOT state that it runs only on Java 8 or 11.

https://clojure.org/releases/downloads says:

Minimum runtime dependency: Java 8
Supported: LTS (long term support) releases, currently Java 8 and Java 11
Others: likely work, but not officially supported

Clojure runs on all versions of Java 8 or higher. We test and officially support Clojure on Java Long Term Support (LTS) releases such as Java 8 or 11 (or coming out today, Java 17). I know of no known issue on any other version of Java 8+, but they are not officially supported.

Clojure works great with Java 16.0.1 - if you want to use that, go for it.

Answer selected: Why tools-deps downloads all deps again when i run the tests (locally and on CI)

Thu, 02 Sep 2021 19:29:48 +0000

Please share a deps.edn that reproduces this.

Answer selected: tools.build.api/git-count-revs should support rev-lists path argument

Mon, 23 Aug 2021 22:46:17 +0000

Good idea - added at 98d1632 for next release.

Answered: Setting --prefix clojure-tools results in the installation being deleted

Mon, 23 Aug 2021 13:51:20 +0000

Logged as https://clojure.atlassian.net/browse/TDEPS-205

Answer selected: getting "Function not found" when invoking clojure with -X:alias

Wed, 18 Aug 2021 18:11:09 +0000

You have a typo in src/web/network_service.clj:

(ns web.netwok-service

There's an r missing so the namespace does not match the filename and cannot be required correctly.

Answer selected: tools.build.api/write-pom does not update scm>tag

Tue, 10 Aug 2021 20:25:56 +0000

Logged as https://clojure.atlassian.net/browse/TBUILD-13

Answer selected: create-basis/java-command do not handle :jvm-opts

Mon, 09 Aug 2021 17:19:49 +0000

Logged as https://clojure.atlassian.net/browse/TBUILD-14

Answer selected: help/doc doesn't work with project dependencies

Thu, 29 Jul 2021 18:02:43 +0000

Logged as https://clojure.atlassian.net/browse/TDEPS-201

Answer selected: Add the CLI equivalent of Leiningen's sample.project.clj

Thu, 29 Jul 2021 00:25:19 +0000

I will update example-deps.edn, that has gotten a little old.

Answer selected: Exception using futures with -X on Clojure CLI 1.10.3.929

Thu, 29 Jul 2021 00:09:00 +0000

I believe with 882, -X called System/exit which is why that version doesn't work.

905 behaves the same way (exits).

912 onward exhibit the "bad" behavior and I'm fairly sure this is because they call shutdown-agents -- which was added to be friendly to exec functions (programs) that would otherwise "hang" at the end.

The root of this change in behavior was probably due to wanting to be able to chain functions -- so the exec functions themselves cannot call shutdown-agents or System/exit because that would "break the chain" and so only the CLI could call those functions once all the exec functions have "completed".

There's an inherent tension between wanting a clean shell exit after calling -X and wanting background threads to stay alive (like the Socket Server example).

Answer selected: help/doc would be useful for -Ttools

Mon, 19 Jul 2021 17:02:49 +0000

Yeah, we have a ticket for this https://clojure.atlassian.net/browse/TDEPS-187

Answer selected: -X:deps help/doc does not work for a function

Thu, 15 Jul 2021 16:19:33 +0000

The correct way to refer to the doc for a function seems to be -X:deps help/doc :fn <ns-name>/<fn-name>:

$ clj -X:deps help/doc :fn clojure.core/cons
-------------------------
clojure.core/cons
([x seq])
  Returns a new seq where x is the first element and seq is
    the rest.

$

But, in this case, that still doesn’t work. Probably, the call to resolve in this line should be requiring-resolve?

Answered: Support for shorthand commands in tools.deps

Sat, 10 Apr 2021 18:15:21 +0000

I am considering a similar feature for babashka. A preview of this has shipped with bb 0.3.3. An example:

https://github.com/borkdude/antq/blob/bb-run/bb.edn

More info: https://github.com/babashka/babashka/issues/778

Answer selected: Support maven mirror with authentication

Thu, 08 Apr 2021 21:59:40 +0000

Logged as https://clojure.atlassian.net/browse/TDEPS-177, thanks for the report. I will try to get that fixed soon.

Feature request -v as an alias for --version when using clojure cli

Wed, 07 Apr 2021 16:48:45 +0000

Running something like clojure -v today with Clojure CLI version 1.10.3.822 will output

WARNING: When invoking clojure.main, use -M
Execution error (FileNotFoundException) at java.io.FileInputStream/open0 (FileInputStream.java:-2).
-v (No such file or directory)

Full report at:
/var/folders/xg/xr5m785j5cb9lm9cjr3qc7480000gn/T/clojure-5319990582198082614.edn

Is it possible to use -v as an alias for clojure --version?

Suggestion - support legacy Homebrew clients

Fri, 12 Feb 2021 12:35:50 +0000

https://github.com/Homebrew/brew/commit/b07685291b65e51e0afc2b6cee91251419e0b3c1 was a breaking change for people deciding to keep using old versions of Brew (which is not particularly easy or popular, but I happen to do it). It's breaking in that an old Brew client querying a newer formula would fail with:

Error: clojure: undefined method `license' for #<Class:0x00007fd2ca91eb38>

This can be trivially addressed by wrapping the license call with an idiomatic if self.respond_to?(:license).

This would allow me to keep using the latest Clojure formulae without having to hack them for such a trivial change.

Would you consider doing it?

Thanks - V

Issue with broken packages if repository doesn't resolve properly

Wed, 11 Nov 2020 16:17:26 +0000

My project edn had a old maven link that no longer resolves, since maven switched to https only in 2020:

:mvn/repos {"central" {:url "http://central.maven.org/maven2/"}

When retrieving deps from a new computer, the packages were all failing with errors like:

Downloading: selmer/selmer/1.12.31/selmer-1.12.31.pom from central
Download corrupted: Checksum validation failed, expected <meta but is ad208edec82716369dab76b6cbca3475a4ae2033

This was because the downloaded "package" were instead HTML files due to AT&T dnsassist.

Since the checksum fails, I would expect the package downloaded to be deleted instead of kept as it is (broken html files). I had to delete the entire .m2, fix the repo link, and then redownload to fix.

Is there a clojure cli equivalent to lein checkouts?

Fri, 13 Mar 2020 14:34:20 +0000

clj allows us to specify local deps with the :local/root coordinate type, but when multiple developers share a deps.edn for a project, it is often the case that they have placed dependencies in different locations on their filesystems. :local/root allows relative paths, which helps with this a bit, but this doesn't allow the flexibility of lein checkouts, which are local file system symlinks that are not stored in version control. Does the clojure cli allow something like that?

No credentials found: deploying Clojars using a Github Workflow (Actions).

Tue, 21 Jan 2020 15:43:33 +0000

For some reason that I can't find, it's impossible for me to deploy Clojars using Github Actions. This is my script where I perform the action.

  - name: Deploy clojars
      run: |
        mkdir ~/.lein
        echo '{:user {} :auth {:repository-auth{#"clojars" {:username "${{ secrets.CLOJARS_USERNAME }}" :password "${{ secrets.CLOJARS_PASSWORD }}" :sign-releases false }}}}' > ~/.lein/profiles.clj
        lein deploy clojars

He's always telling me he can't find the credentials.

No credentials found for clojars
    See `lein help deploying` for how to configure credentials to avoid prompts.
    Username: LEIN IS UNABLE TO TURN OFF ECHOING, SO THE PASSWORD IS PRINTED TO THE CONSOLE
    Password: Created /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar
    Wrote /home/runner/work/tadam-core/tadam-core/pom.xml
    Need to sign 2 files with GPG
    [1/2] Signing /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar with GPG
    gpg: directory '/home/runner/.gnupg' created
    gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
    gpg: no default secret key: No secret key
    gpg: signing failed: No secret key
    Could not sign /home/runner/work/tadam-core/tadam-core/target/tadam-core-0.3.0.jar
    gpg: directory '/home/runner/.gnupg' created
    gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
    gpg: no default secret key: No secret key
    gpg: signing failed: No secret key
    
    
    See `lein help gpg` for how to set up gpg.
    If you don't expect people to need to verify the authorship of your jar, you
    can add `:sign-releases false` to the relevant `:deploy-repositories` entry.
    ##[error]Process completed with exit code 1.

Using git deps in a restricted environment

Tue, 19 Nov 2019 09:19:20 +0000

As tools.deps gains traction, there are some libraries that are only available via git, eg cognitect-labs/test-runner.

In some corporate environments without git (or general internet) access, where dependencies are acquired via tools like artifactory (for maven, npm etc), such libraries are troublesome to use.

In such cases, what would your recommended approach be?

find another library
publish the library to maven either by yourself or asking the maintainers
copy the source into your own source
fork it into an internal (intranet) git repo and use that as a dependency

Why is clojure not picking up installation level deps.edn?

Thu, 07 Nov 2019 04:01:55 +0000

I have a fresh install of clojure 1.10.1.483 on a RHEL7 docker image, with the repos in /usr/local/lib/clojure/deps.edn (the installation level config) modified to point to our corporate artifactory repository.

However, despite the -Sverbose option saying the file is in the config_paths, these repos are not picked up if running anywhere outside the directory itself.

Doing something like clojure -e “(clojure-version)”

works from within the installation dir as the deps.edn is picked up as the ‘project’ config. This indicates there is nothing wrong with the config itself.
fails in any other dir, saying it cannot connect to the default repos (repo1.maven.org etc), which do not exist in any config file being checked.

User level config is default (all commented) so should not impact, but -Srepro makes no difference.

I can only conclude that the installation level config is not picked up correctly.

Does anyone have any pointers here?

Why does -A not merge deps across multiple aliases in tools.deps?

Tue, 05 Nov 2019 03:38:08 +0000

The deps reference says the -A option applies across all alias types. It also says if multiple -R alias maps are specified, they are merged. This to me implies that if only options available to -R are specified (like :extra-deps), then multiple -A maps will behave the same as multiple -R maps.

Given the above, and two aliases with just :extra-deps specified, I expect the following to be equivalent:

clojure -R:a:b -Spath
clojure -A:a:b -Spath

However, while -R generates a path with the deps of both :a and :b, the -A version only contains the deps of :b.

Is this a bug or is the behaviour intentionally different?

I tested this on the latest windows clojure 1.10.1.483

Running Chestnut in Cursive

Wed, 23 Oct 2019 13:32:23 +0000

Has anyone tried setting up a chestnut template in Cursive? It seems like the way IDEA auto saves causes the hot loader to not recognize the changes being made; preventing it loading those changes in the browser.