-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make repl
fails to start a REPL with Leiningen 2.11.x
#848
Comments
Hi! Thank you for using CIDER (and presumably, enrich-classpath?). There's not enough information in this issue for it to be actionable. Plese attach stacktraces if any. The issue should also be reproducible in a project that we can clone. Feel free to reopen the issue as you gather that info. |
Probably a misunderstanding. Lines 72 to 73 in 9aea519
I'm actually trying to investigate an issue in |
Sorry about the misunderstanding - I thought this issue had been created in https://github.com/clojure-emacs/cider Either way, But |
Can you please reveal which version of Clojure/Lein/Java it works on?
Any idea what could be the cause? |
The Clojure version is managed by Leiningen
Perhaps try a I also heard that the most recent Lein broke some plugins https://codeberg.org/leiningen/leiningen/pulls/39 - don't know if we're affected Hope it helps! |
Thanks. Had a clean repo already. |
make repl
fails to start a REPLmake repl
fails to start a REPL with Leiningen 2.11.x
This issue should probably be reopened with the new title, but it doesn't seem like I can do that. |
Happy we got it! |
There's the open PR in Lein. There's nothing we can do about it but wait. Feel free to ping them |
Ah, alright. |
Expected behavior
REPL should appear
Actual behavior
Steps to reproduce the problem
Environment & Version information
cider-nrepl version
Current master
v0.45.0
v0.44.0
Java version
Operating system
macOS 10.15.7
Linux Devuan Daedalus
Leiningen & Clojure versions
Leiningen 2.11.1 on Java 19.0.1 OpenJDK 64-Bit Server VM
Clojure CLI version 1.11.1.1435
The text was updated successfully, but these errors were encountered: