This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-21
Channels
- # announcements (4)
- # architecture (161)
- # autochrome-github (7)
- # babashka (61)
- # beginners (42)
- # calva (24)
- # cider (22)
- # clj-kondo (28)
- # cljs-dev (8)
- # clojure (88)
- # clojure-art (2)
- # clojure-dev (7)
- # clojure-europe (43)
- # clojure-germany (2)
- # clojure-nl (2)
- # clojure-uk (4)
- # clojurescript (32)
- # core-async (41)
- # cursive (32)
- # datahike (6)
- # datomic (9)
- # emacs (22)
- # events (2)
- # fulcro (10)
- # graphql (1)
- # nextjournal (16)
- # off-topic (9)
- # overtone (1)
- # pathom (16)
- # polylith (5)
- # quil (7)
- # rdf (1)
- # re-frame (7)
- # reagent (22)
- # releases (2)
- # remote-jobs (1)
- # reveal (12)
- # sci (1)
- # shadow-cljs (12)
- # specter (20)
- # sql (6)
- # tools-deps (21)
- # vim (26)
- # xtdb (10)
A plugin I'm developing can cause this section to fail https://github.com/clojure/clojure/blob/clojure-1.10.3/src/clj/clojure/core.clj#L7057-L7074 since clojure/version.properties
would be absent apparently (not my project; hard to repro)
Does that sound familiar at all?
"plugins" often have weird classloader stuff going on, baseLoader may be returning a classloader that doesn't have access to clojure
My plugin deliberately avoids classloader stuff. It adds stuff to the classpath by simpler means. But I don't see how it could make clojure.core be loaded while clojure/version.properties
would be absent or otherwise malformed
i.e. all jars are left as-is of course, I expect a .jar to be "atomic" so this issue catches me off-guard.
if you are using a plugin for an existing java based system, those often doing weird things with classloaders to try and isolate plugins with each other