there is a new pre-release of the CLI available if anyone wants to try it, version 1.11.1.1435: • TDEPS-238 - deps.edn files are now validated against specs • TDEPS-239 - treat empty deps.edn file as {} • Updated several dependencies (kind of an interim point towards resolving the maven dep library upgrade) • Removed the guava dependency, which is big and always lagging cve-wise, and afaict was not needed as we don't use guice injection in maven
just re-bumping this in case anyone missed it last week, would be happy to see any extra eyeballs
ran it over the libraries tracked in core-regression, and all deps.edn tests passed, so that's 66 big-name libraries that are good to go
thx
I am getting an error when starting a repl with nrepl that wasnt there before I upgraded Clojure CLI to the pre-release (it could be a change in the nrepl library itself)
Execution error (FileNotFoundException) at nrepl.cmdline/require-and-resolve (cmdline.clj:221).
Could not locate cider/nrepl__init.class, cider/nrepl.clj or cider/nrepl.cljc on classpath.
I've tried it on an empty project and an existing project with a few different alias. I'll see if I can find out more infoCurious, an error is happening with cider/cider-nrepl 44.0 but the pre-release seems to work okay with 43.3, so probably an issue with Cider
False alarm, it seems its an issue with Cider-nrepl 0.44.0 that I hadnt noticed before.
(~/clojure)-(!2005)-> clj -version
Clojure CLI version 1.11.1.1435
Tue Jan 02 15:20:15
(~/clojure)-(!2006)-> clj -Sdeps '{:deps {cider/cider-nrepl {:mvn/version "0.43.3"}}}'
Downloading: cider/cider-nrepl/0.43.3/cider-nrepl-0.43.3.pom from clojars
Downloading: cider/orchard/0.20.0/orchard-0.20.0.pom from clojars
Downloading: cider/orchard/0.20.0/orchard-0.20.0.jar from clojars
Downloading: cider/cider-nrepl/0.43.3/cider-nrepl-0.43.3.jar from clojars
Clojure 1.12.0-alpha5
user=> (require 'cider.nrepl)
nil
user=>
Tue Jan 02 15:20:43
(~/clojure)-(!2007)-> clj -Sdeps '{:deps {cider/cider-nrepl {:mvn/version "0.44.0"}}}'
Downloading: cider/cider-nrepl/0.44.0/cider-nrepl-0.44.0.pom from clojars
Downloading: cider/orchard/0.21.0/orchard-0.21.0.pom from clojars
Downloading: cider/cider-nrepl/0.44.0/cider-nrepl-0.44.0.jar from clojars
Downloading: cider/orchard/0.21.0/orchard-0.21.0.jar from clojars
Clojure 1.12.0-alpha5
user=> (require 'cider.nrepl)
nil
user=>
point_up::skin-tone-2 more complicated than this case, which works?Nope, same three dependencies and the same main-opts as I've use for a while...
;; clojure -M:repl/rebel
:repl/rebel
{:extra-deps {nrepl/nrepl {:mvn/version "1.1.0"}
cider/cider-nrepl {:mvn/version "0.44.0"}
com.bhauman/rebel-readline {:mvn/version "0.1.4"}}
:main-opts ["--eval" "(apply require clojure.main/repl-requires)"
"--main" "nrepl.cmdline"
"--middleware" "[cider.nrepl/cider-middleware]"
"--interactive"
"-f" "rebel-readline.main/-main"]}
Looks like it was a corrupted download for that library dependency. I nuked the local maven repo and the pre-release and latest release of the Clojure CLI are working (which gave an opportunity for the pre-release to download all my dependencies again) Also successfully tested a project with an empty deps.edn
I'll put that in place at work in about 20 mins to see how things go 🙂 and then I'll run tests on all my OSS projects.
Thx
Ran it across every OSS project I (running tests, running build.clj targets) and also a full build cycle at work (lots of build.clj targets etc) and found no problems. I'm now running clojure -X:deps list in every folder on my machine that has a deps.edn file! 🙂
That was about 250 random projects or project fragments. No problems found in any of them.
What’s the best way to run this temporarily?
You can use one of the install scripts here https://github.com/clojure/brew-install/releases/tag/1.11.1.1435 and then use the regular install script to re-install 1.11.1.1429 if you need to.
If you use brew you can install a specific version: brew install clojure/tools/clojure@1.11.1.1435 (and target 1.11.1.1429 if you need to revert).
Ah great, thanks Sean
The guava removed is an awesome change!
particularly, if you try it and don't see any issues, would appreciate a 👍 here. while I did check TDEPS-238 against a corpus of deps.edn's I had lying around, would hate to start failing a deps.edn load somewhere. for TDEPS-239, cc @pez as he was looking for that for Calva. I will plan to promote this to new stable sometime next week unless I hear otherwise.
doing the maven core dep updates to 3.9.x is going to take some re-work but I've charted a course towards that
if this path works (still tbd), I think it will be a big step forward in terms of clean use of maven resolver and associated deps, should be able to kill off some more deps