Migration plans for nREPL 0.4 #695
Comments
|
It sounds like a good approach for me. |
bbatsov
added a commit
to bbatsov/boot
that referenced
this issue
Jun 26, 2018
nREPL was recently moved out of clojure-contrib and it's developed continued under a dedicated org. The new project is (and will remain to be) completely backwards compatible on the nREPL API level, but the namespace had to be changed. This fixes boot-clj#695.
Merged
bbatsov
added a commit
to bbatsov/boot
that referenced
this issue
Jun 29, 2018
nREPL was recently moved out of clojure-contrib and it's developed continued under a dedicated org. The new project is (and will remain to be) completely backwards compatible on the nREPL API level, but the namespace had to be changed. This fixes boot-clj#695.
|
I like the idea of adding a new |
|
@alandipert I'm not sure if that makes sense any more, as pretty much all of the essential middleware got updated to support nREPL 0.4 while this and #703 stayed open. Seems to me at this point it would just be simpler to directly switch to 0.4 (and that's also what lein did already - it switch to nREPL 0.4 in If you insist on a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
That's basically a follow up of nrepl/nrepl#1 and was also discussed in nrepl/nrepl#4.
TL;DR; - In verions 0.4 of the "new" nREPL the namespaces will be changed from
clojure.tools.nrepl.*tonrepl.*.As this is a different artifact technically speaking(
nrepl/nreplinstead ofclojure.tools/nrepl) I think the best migration path for Boot would be to just start depending on both projects and have two tasks for the two nREPLs until we can drop the old version (e.g.boot replandboot nrepl). The second task can just start a headless server until reply adds support fornrepl/nrepl.How does this sound?
The text was updated successfully, but these errors were encountered: