About A faithful port of the clojure CLI bash script to Clojure. Used as native CLI, deps resolver in babashka and getting started REPL in Calva.
Clojure provides the clojure
command line tool for:
The clojure
CLI is written in bash. This is a port of that tool written in
Clojure itself.
Features:
cmd.exe
on WindowsLinux and macOS:
$ bash <(curl -s https://raw.githubusercontent.com/borkdude/deps.clj/master/install)
$ deps
Clojure 1.10.1
user=>
Windows:
C:\> PowerShell -Command "iwr -useb https://raw.githubusercontent.com/borkdude/deps.clj/master/install.ps1 | iex"
C:\> deps.exe
Clojure 1.10.1
user=>
If your Windows system does not run PowerShell, you can simply download a Windows binary from Github releases and place it on your path.
Originally this project was created as a proof of concept to see if the
clojure
bash script could be ported to Clojure and be used as a
babashka script.
Nowadays it is used as the code behind the babashka.deps
namespace and the
clojure
subcommand in babashka, to resolve and download dependencies for
babashka itself, or when running a Clojure process with babashka.
This project offers an arguably easier way to get going with deps.edn
based
projects in CI. Just download an installer script, execute it with bash or
Powershell and you're set. Installer scripts are provided for linux, macOS and
Windows.
Windows users might find the deps.exe
executable of value if they have trouble
getting their system up and running. It works with cmd.exe
unlike the current
Powershell based approach.
Available under the clojure
subcommand. It is also available as
a programmatic API under babashka.deps
.
Used to provide a getting started REPL.
Deps.clj tries to follow the official Clojure CLI as faithfully as possible and as such, this project can be considered a stable drop-in replacement. Experimental extra options may still be changed or removed in the future.
There are three ways of running:
deps
which is tailored to your OS.deps.clj
using the bb
or clojure
runtime.The binary version of deps.clj, called deps
(without the .clj
extension), only requires a working
installation of java
.
Binaries for linux, macOS and Windows can be obtained on the Github releases page.
Install using the installation script on linux or macOS:
$ bash <(curl -s https://raw.githubusercontent.com/borkdude/deps.clj/master/install) /tmp
$ /tmp/deps
Clojure 1.10.1
user=>
On Windows you might want to install deps.clj
using
scoop.
Alternatively you can install deps.exe
using by executing the following line:
C:\> PowerShell -Command "iwr -useb https://raw.githubusercontent.com/borkdude/deps.clj/master/install.ps1 | iex"
C:\> deps.exe
Clojure 1.10.1
user=>
It's automatically added to your path. In Powershell you can use it right away. In cmd.exe
you'll have to restart the session for it to become available on the path.
When you get a message about a missing MSVCR100.dll
, also install the
Microsoft Visual C++ 2010 Redistributable Package
(x64) which is
also available in the
extras
Scoop bucket.
The script, deps.clj
, requires a working installation of java
and
additionally bb
or clojure
.
It can simply be downloaded from this repo:
$ curl -sL https://raw.githubusercontent.com/borkdude/deps.clj/master/deps.clj -o /tmp/deps.clj
$ chmod +x /tmp/deps.clj
$ bb /tmp/deps.clj
Clojure 1.10.1
user=>
On Windows you can use the deps.bat
script:
C:\Temp> curl -sL https://raw.githubusercontent.com/borkdude/deps.clj/master/deps.bat -o c:\Temp\deps.bat
C:\Temp> deps
C:\Temp>
Clojure 1.10.1
user=>
This project will look in $HOME/.deps.clj/<clojure-version>/ClojureTools
for
clojure-tools-<clojure-version>.jar
, exec.jar
and example-deps.edn
. If it
cannot it find those files there, it will try to download them from
this
location. You can override the location of these jars with the
DEPS_CLJ_TOOLS_DIR
environment variable. If the download fails for some reason,
you can try to download the zip yourself and unzip it at the expected location.
If you have an already installed version of clojure using e.g. brew, you can set
DEPS_CLJ_TOOLS_DIR
to that directory:
This project assumes a specific version of the tools jar. However, it can be desirable to up- or downgrade the targetted tools jar in case of bug fixes or bugs in newer versions. Be aware that the code of this project is written with a specific version of the tools jar in mind, so use this at your own risk. Given that there isn't a lot of churn in the bash code that this project replaces, the risk should be relatively low.
The deps.clj
script adds the following features compared to the clojure
tool:
-Sdeps-file Use this file instead of deps.edn
-Scommand A custom command that will be invoked. Substitutions: {{classpath}}, {{main-opts}}.
It also is able to pick up proxy information from environment variables.
One of the use cases for deps.clj
is invoking a different command than java
.
Given this deps.edn
:
{:aliases
{:test
{:extra-paths ["test"]
:extra-deps {borkdude/spartan.test {:mvn/version "0.0.4"}}
:main-opts ["-m" "spartan.test" "-n" "borkdude.deps-test"]}}}
you can invoke bb
like this:
$ deps.clj -A:test -Scommand "bb -cp {{classpath}} {{main-opts}}"
Ran 3 tests containing 3 assertions.
0 failures, 0 errors.
If you use -Scommand
often, an alias can be helpful:
$ alias bbk='rlwrap deps.clj -Scommand "bb -cp {{classpath}} {{main-opts}}"'
$ bbk -A:test
Ran 3 tests containing 3 assertions.
0 failures, 0 errors.
The bbk
alias is similar to the clj
alias in that it adds rlwrap
.
Additional args are passed along to the command:
$ bbk -e '(+ 1 2 3)'
6
Of course you can create another alias without rlwrap
for CI, similar to the
clojure
command:
$ alias babashka='deps.clj -Scommand "bb -cp {{classpath}} {{main-opts}}"'
This approach can also be used with planck or lumo:
$ alias lm='deps.clj -Scommand "lumo -c {{classpath}} {{main-opts}}"'
$ lm -Sdeps '{:deps {medley {:mvn/version "1.2.0"}}}' -K \
-e "(require '[medley.core :refer [index-by]]) (index-by :id [{:id 1} {:id 2}])"
{1 {:id 1}, 2 {:id 2}}
The -Sdeps-file
option may be used to load a different project file than deps.edn
.
deps.clj supports setting a proxy server via the "standard" environment variables (the lowercase versions are tried first):
http_proxy
or HTTP_PROXY
for http traffichttps_proxy
or HTTPs_PROXY
for https trafficThis will set the JVM properties -Dhttp[s].proxyHost
and -Dhttp[s].proxyPort
.
The format of the proxy string supported is http[s]://[username:password@]host:port
. Any username and password info is ignored as not supported by the underlying JVM properties.
For running locally, you can invoke deps.clj with clojure
(totally meta
right?). E.g. for creating a classpath with deps.clj, you can run:
$ clojure -M -m borkdude.deps -Spath
or with lein
:
$ lein run -m borkdude.deps -Spath
To run jvm tests:
$ script/jvm_test
To run with babashka after making changes to src/borkdude/deps.clj
, you should run:
$ script/gen_script.clj
and then:
$ ./deps.clj -Spath
# or
$ bb deps.clj -Spath
To run as an executable, you'll first have to compile it. First,
download a GraalVM
distro. The compile script assumes that you will have set GRAALVM_HOME
to the
location of your GraalVM installation. Currently this project uses java-11-20.1.0
.
$ export GRAALVM_HOME=/Users/borkdude/Downloads/graalvm-ce-java11-20.1.0/Contents/Home
The script also assumes that you have
lein
installed.
Run the compile script with:
$ script/compile
If everything worked out, there will be a deps
binary in the root of the
project.
To run executable tests:
$ script/exe_test
Copyright © 2019-2020 Michiel Borkent
Distributed under the EPL License. See LICENSE.
This project is based on code from clojure/brew-install which is licensed under the same EPL License.
Can you improve this documentation? These fine people already did:
Michiel Borkent & sundbpEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close