This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-05-16
Channels
- # announcements (1)
- # babashka (13)
- # beginners (33)
- # calva (26)
- # cherry (33)
- # clerk (5)
- # clj-kondo (3)
- # clojure (40)
- # clojure-europe (24)
- # clojure-finland (2)
- # clojure-norway (29)
- # clojurescript (18)
- # cursive (2)
- # datomic (6)
- # docker (11)
- # emacs (12)
- # events (1)
- # fulcro (71)
- # graalvm (8)
- # hyperfiddle (2)
- # lsp (23)
- # meander (5)
- # off-topic (36)
- # polylith (4)
- # re-frame (6)
- # reitit (13)
- # shadow-cljs (87)
- # spacemacs (1)
- # tools-deps (19)
- # vim (5)
- # xtdb (57)
Is there any guidance on using non-clojure PolyProjects in your codebase? I thought I saw some info on this somewhere, but can't find it now. Currently, adding non Clojure projects into the projects/
dir causes the tool to break
One way is to create another directory that lives side by side with projects
, e.g. java-projects
or something. Another solution could be to put your Clojure workspace inside a top top directory of your repository, e.g. clojure
and then have another top directory, e.g. java
, where you put your Java code (e.g. inside a projects
directory). Java is of course just an example!
Thanks for the input, we independently came up with your first solution, so I think there is probably something to it.
For other interested readers: an alternative we discussed was to put an empty deps.edn
into each of the non-clojure polylith projects inside of projects/
. I didn't test if it worked or not but it seems like another reasonable solution