@@ -79,11 +79,29 @@ add `piggieback` as well. The injection mechanism is configurable and
79
79
you can easily add more libraries there. Some CIDER extensions would use
80
80
this mechanism to auto-inject their own dependencies.
81
81
82
- CIDER would also inject the most recent version of nREPL that it supports. This is a simple
83
- trick to override the version of nREPL bundled with your build tool, so you can gain
82
+ Here's how you can modify the injected dependencies for `cider-jack-in-clj`:
83
+
84
+ [source,lisp]
85
+ ----
86
+ ;; auto-inject version 1.0 of the library foo/bar
87
+ (cider-add-to-alist 'cider-jack-in-dependencies
88
+ "foo/bar" "1.0")
89
+ ----
90
+
91
+ CIDER will also inject the most recent version of nREPL that it supports. This is a simple
92
+ trick to override the version of nREPL bundled with your build tool (e.g. Leiningen), so you can gain
84
93
access to the newest nREPL features. Generally that's one aspect of CIDER's inner workings
85
94
that end-users will rarely have to think about.
86
95
96
+ You can override the injected versions of `cider-nrepl` and nREPL by customizing
97
+ `cider-injected-middleware-version` and `cider-injected-nrepl-version`.
98
+ Generally you should avoid doing this, but it may be useful if you want to try
99
+ a newer version or you encounter some regression that forces you to temporarily use
100
+ an older version.
101
+
102
+ NOTE: You'll have to restart Emacs for such changes to take effect, if you've already loaded CIDER. Alternatively you can update
103
+ manually the underlying dependencies list (e.g. `cider-jack-in-dependencies`).
104
+
87
105
CIDER can also inject a Clojure dependency into your project, which is useful,
88
106
for example, if your project defaults to an older version of Clojure than that
89
107
supported by the CIDER middleware. Set `cider-jack-in-auto-inject-clojure`
0 commit comments