This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-23
Channels
- # announcements (10)
- # babashka (7)
- # beginners (31)
- # boot (4)
- # calva (8)
- # chlorine-clover (19)
- # cider (12)
- # clj-kondo (27)
- # cljsrn (7)
- # clojure (68)
- # clojure-colombia (2)
- # clojure-europe (47)
- # clojure-italy (16)
- # clojure-nl (4)
- # clojure-spec (13)
- # clojure-uk (39)
- # clojurescript (103)
- # code-reviews (8)
- # community-development (2)
- # conjure (38)
- # core-async (37)
- # cursive (2)
- # datascript (1)
- # datomic (31)
- # figwheel-main (22)
- # fulcro (18)
- # jobs (2)
- # jobs-discuss (6)
- # juxt (3)
- # keechma (1)
- # lambdaisland (6)
- # malli (30)
- # meander (20)
- # off-topic (29)
- # reagent (1)
- # reitit (16)
- # shadow-cljs (4)
- # tools-deps (70)
- # xtdb (19)
I was told a while ago to commit .idea/clojure-deps.xml to version control. I think it had something to do with branch switching not remembering your projects. While commiting it does solve that problem, it brings up a bunch of other issues. I don't have a repro but our team continually gets projects added or removed from the list without explicitly doing so. Also, adding a project outside of the git root will cause issues for everyone else that doesn't have that directory available. Is committing .idea/clojure-deps.xml still the right approach to get projects kept when switching git branches?
i usually don't have issues with that specific file, although the list in the <option name="projectFiles">
section might get reordered arbitrarily.
however, the upcoming intellij version would like to convert the configuration directory, so i can imagine that would confuse earlier versions, so im not yet switching to the next EAP, though it's in RC stage now.