You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Gradle support was originally added to cider in 2015, the default
was set to disable Gradle's daemon [1] which Gradle uses to keep a warm
JVM around to reuse for future runs.
While I know there are some strong opinions about its use of a daemon,
this is the default behavior of Gradle and I don't think we have any
strong reasons to disable it in this case.
It's possible in 2015 the daemon was less stable or more of a hog, but I
don't believe that's true nowadays.
[1] https://docs.gradle.org/current/userguide/gradle_daemon.html
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@
11
11
12
12
* Upgrade injected `cider-nrepl` to [0.28.5](https://github.com/clojure-emacs/cider-nrepl/releases/tag/v0.28.5).
13
13
*[#3200](https://github.com/clojure-emacs/cider/issues/3200): Improve cider-browse-ns interface to allow selective hiding of var types as well as grouping options. Include private vars in result list.
14
+
* Changed default `cider-gradle-command` to `./gradlew` to use the Gradle wrapper
15
+
* Changed default `cider-gradle-global-options` to `""` (empty, formerly `--no-daemon`)
0 commit comments