Fork me on GitHub
#tools-deps
<
2019-04-05
>
rafael21:04:28

I'm seeing an Error building classpath message when running clj. I'm running with -Sverbose but it doesn't help to identify the problematic dependency.

rafael21:04:26

$ clj -Sverbose -Sdeps '{:deps {org.clojure/clojure {:mvn/version "1.9.0"} midje {:mvn/version "1.9.7"}}}' 
version      = 1.9.0.329
install_dir  = /nix/store/i2zsj4qknknpfrvfhpx0z69c44b0c12j-clojure-1.9.0.329-prefix
config_dir   = /home/rafael/.clojure
config_paths = /nix/store/i2zsj4qknknpfrvfhpx0z69c44b0c12j-clojure-1.9.0.329-prefix/deps.edn /home/rafael/.clojure/deps.edn deps.edn
cache_dir    = .cpcache
cp_file      = .cpcache/2657530762.cp

Refreshing classpath
Error building classpath. In the dependency graph, library org.clojure/clojure specifies version range "[1.2.1],[1.3.0]" - please specify a version in your configuration.

rafael21:04:48

Should I open an issue? I'm having a hard time finding out how to proceed debugging the problem.

Alex Miller (Clojure team)21:04:43

Update your clj version

Alex Miller (Clojure team)21:04:24

Some older versions like this one didn’t handle version ranges

rafael21:04:13

Newbie question: is there a way to test a new clj version without updating the binary installed in the system?

lilactown21:04:11

I think it's literally a shell script, you could try downloading it and executing it in a local dir?

Alex Miller (Clojure team)21:04:41

It’s both a script and an uberjar

Alex Miller (Clojure team)21:04:37

They need to be matched up

Alex Miller (Clojure team)21:04:07

There isn’t an easy way to do what you’re asking but you could always rollback to the version you’re on - it’s just the same url with the version you want