This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-28
Channels
- # announcements (9)
- # aws (2)
- # beginners (45)
- # biff (2)
- # calva (20)
- # cider (4)
- # cljdoc (15)
- # cljs-dev (9)
- # clojure (102)
- # clojure-austin (14)
- # clojure-europe (39)
- # clojure-france (3)
- # clojure-germany (1)
- # clojure-norway (39)
- # clojure-spec (1)
- # clojure-uk (3)
- # conjure (8)
- # cursive (6)
- # datahike (3)
- # datomic (8)
- # emacs (28)
- # events (1)
- # holy-lambda (6)
- # hyperfiddle (13)
- # jobs (11)
- # keechma (2)
- # lsp (4)
- # malli (34)
- # nbb (36)
- # off-topic (52)
- # pathom (5)
- # pedestal (2)
- # portal (1)
- # reagent (2)
- # reitit (3)
- # remote-jobs (1)
- # scittle (1)
- # spacemacs (2)
- # xtdb (5)
How can you prevent a module from being managed by maven?
15.12 Maven module detected: Module x is managed by Maven and cannot be managed by Leiningen at the same time.
I also have the following error in the run configuration for the module:
Run Configuration Error: The Clojure jar is not attached to this module
And what I’m really trying to solve is not the error messages, but that Cursive does not recognise the code:
Removing and re-adding the module “fixed” these problems. I learned nothing about what caused them, though 🙂 🤡
Maybe the error messages are related, maybe not, idk
Has anyone had cursive “run away” on cpu usage? For some reason in the past 2 weeks this has happened 3 times, where cursive starts taking ~500% cpu until I kill it. FWIW I’m on a brand new M1 mbp. I captured a performance profile from IJ last time this happened if that’s helpful. It seems to be related to indexing kicking off, though it continues well after indexing has finished
Removing and re-adding the module “fixed” these problems. I learned nothing about what caused them, though 🙂 🤡