This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-29
Channels
- # adventofcode (9)
- # announcements (2)
- # aws (78)
- # babashka (55)
- # beginners (97)
- # biff (9)
- # calva (11)
- # cherry (2)
- # cider (8)
- # clerk (7)
- # clj-kondo (6)
- # clj-on-windows (4)
- # clojure (213)
- # clojure-austin (6)
- # clojure-europe (63)
- # clojure-nl (1)
- # clojure-norway (5)
- # clojure-spec (10)
- # clojure-uk (1)
- # clojurescript (14)
- # clr (2)
- # community-development (3)
- # conjure (14)
- # datomic (2)
- # deps-new (5)
- # dev-tooling (10)
- # editors (3)
- # emacs (3)
- # etaoin (19)
- # events (4)
- # fulcro (71)
- # holy-lambda (20)
- # java (3)
- # jobs (2)
- # leiningen (4)
- # lsp (24)
- # malli (15)
- # membrane (107)
- # music (1)
- # off-topic (29)
- # pedestal (4)
- # polylith (1)
- # portal (2)
- # rdf (5)
- # releases (7)
- # scittle (5)
- # shadow-cljs (8)
- # tools-build (15)
- # tools-deps (6)
- # xtdb (13)
The homebrew formula for lein pulls in a dependency on openjdk
which is currently on java 19. I think this is problematic because clojure only officially supports LTS releases of Java, of which Java 19 is not. https://clojure.org/releases/downloads#_java_compatibility
Just want to get a feel for if others agree that this is problematic. I know that I can configure the version of java on a global or per project basis, but I think it’s still a problem that the brew formula pulls in an unsupported version of java.
I'm developing on java19 for a while without problem. Personally, I like to switch between java19-11, correto, graalvm, or any other JVM, to ensure that the project is JVM-resilient. The projects that I work on runs a CI with a specific java11 version.
this is a brew policy (which is very dumb imo), and is the reason why we maintain our own brew tap for the Clojure CLI with a formula that does not depend on Java
while we only officially test and support Clojure on LTS releases, I do test it with each intermediate version and generally our requirements are fairly conservative, so I don't know of any non-LTS version that has any issues (including Java 19), so I would not see this as a cause for worry