This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-03
Channels
- # aleph (2)
- # announcements (13)
- # babashka (7)
- # beginners (36)
- # calva (26)
- # cider (11)
- # circleci (13)
- # clj-kondo (15)
- # clojure (105)
- # clojure-europe (79)
- # clojure-nl (3)
- # clojure-uk (6)
- # clojurescript (17)
- # conjure (4)
- # core-logic (2)
- # cursive (10)
- # data-science (5)
- # datalevin (11)
- # datalog (14)
- # eastwood (6)
- # emacs (2)
- # figwheel-main (1)
- # fulcro (34)
- # google-cloud (1)
- # graphql (3)
- # introduce-yourself (7)
- # jobs (1)
- # leiningen (17)
- # lsp (46)
- # malli (2)
- # minecraft (3)
- # missionary (19)
- # off-topic (31)
- # other-languages (49)
- # polylith (2)
- # portal (5)
- # practicalli (1)
- # quil (77)
- # releases (1)
- # remote-jobs (1)
I tried to use "Clojure Application" configuration to run my custom namespaces that kicks off my repl. I noticed that if I choose "Run with Deps" I got:
class java.lang.Character cannot be cast to class java.lang.String (java.lang.Character and java.lang.String are in module java.base of loader 'bootstrap')
while when I choose "Run with IntelliJ proejct classpath" it starts ok (but complains later because the given namespace does not exist in the classpath because it is added only in specific deps alias - I guess this part is normal).There’s an issue for this, I’ll look at it for the next EAP: https://github.com/cursive-ide/cursive/issues/2617
Just curious: how often do y’all update IntelliJ? I think I had one bad experience 2 or 3 years ago, and so now I update maybe once per year. (I just learned you can upgrade Cursive independent of IntelliJ upgrades! Duh.)
I had a bad experience once, but the most I've done is stopped using EAPs. I "survived" the OSX update that nuked Java (by "survived", I mean I moved to a PC for several years), so my threshold is a bit higher. 😄
I am on the EAP channel of both IJ and Cursive. For IJ I usually upgrade to builds that my must-have plugins support unless I see problems posted in this channel. For Cursive I usually upgrade at the first opportunity after a new build comes out
is it possible to disable (ideally temporarily) the Aviso exception printer when running a test?
in essence, I’m running into this: