This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-03
Channels
- # announcements (5)
- # babashka (7)
- # beginners (119)
- # biff (4)
- # cider (7)
- # clj-kondo (26)
- # cljfx (3)
- # cljs-dev (2)
- # clojure (28)
- # clojure-austin (18)
- # clojure-europe (9)
- # clojure-france (6)
- # clojure-norway (4)
- # clojure-uk (3)
- # clojurescript (6)
- # community-development (1)
- # core-async (4)
- # cursive (9)
- # data-science (12)
- # datomic (13)
- # duct (18)
- # emacs (15)
- # etaoin (5)
- # events (13)
- # honeysql (46)
- # hyperfiddle (9)
- # jackdaw (5)
- # jobs (13)
- # keechma (4)
- # lsp (37)
- # malli (32)
- # nbb (14)
- # off-topic (10)
- # other-languages (2)
- # polylith (4)
- # programming-beginners (3)
- # reagent (27)
- # reitit (1)
- # shadow-cljs (32)
- # sql (11)
- # tools-build (5)
- # tools-deps (3)
- # vim (14)
- # xtdb (11)
Has anyone ran into this kind of an issue that when Idea is restarted, the module settings automatically generate additional content roots based on the source-paths given in the project.clj file? These extra content roots cause that the “find usages” feature breaks and doesn’t work from the “common” module to the other modules. The common project is code shared by a few different projects and this same issue is in all of the projects that are using the shared project in the source path. Is there some better way to manage this so these extra content roots are not generated or can I somehow stop idea from analyzing project sources on each startup and every time some dependencies change?
The other approach to this is that you use https://codeberg.org/leiningen/leiningen/src/branch/stable/doc/TUTORIAL.md#checkout-dependencies in which the commonly shared project which is being developed simultaneously is added to the /checkouts/
folder as a symlink, but that causes the common module to get all kinds of crazy with the content roots. And this happens everytime you restart Idea or the dependencies change.
This pretty minor inconvenience is driving me nuts, and would really appreciate if anyone had any insight as to how this kind of project structure should be managed with Idea. 😄
Yes, checkout dependencies have some issues at the moment, I’ll try to look at them soon. It’s definitely the case that IntelliJ only likes one module at a time to be using a single source root. I’m looking at a similar issue at the moment with deps, so I’ll try to look at this in the next couple of days.
@UMBC73RK9 you are using lein checkout
?
I'm trying to use it. Using REPL
with Run with Lein
etc
but it never includes my checkouts in the classpath,
Do you mean this https://github.com/timvisher/lein-checkout? If you do we are not using that, we just created the checkouts folders ourself and added those to the source-paths where necessary
I can't understand how cursive works with https://mvnrepository.com/artifact/lein-parent/lein-parent but do not work with lein-checkout. Does it have special code to handle lein parent @U0567Q30W?