This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-25
Channels
- # announcements (8)
- # babashka (58)
- # beginners (59)
- # biff (4)
- # calva (39)
- # cider (2)
- # clj-kondo (8)
- # clj-together (4)
- # cljdoc (5)
- # cljsrn (1)
- # clojure (60)
- # clojure-australia (2)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (3)
- # clojurescript (13)
- # conjure (10)
- # cursive (9)
- # datomic (5)
- # dev-tooling (1)
- # emacs (6)
- # events (1)
- # graalvm (38)
- # graphql (5)
- # joyride (1)
- # kaocha (3)
- # lsp (23)
- # malli (2)
- # mount (2)
- # off-topic (31)
- # other-languages (13)
- # pathom (3)
- # polylith (12)
- # portal (4)
- # practicalli (22)
- # re-frame (6)
- # reagent (3)
- # releases (3)
- # sql (4)
- # squint (3)
- # tools-build (10)
- # tools-deps (10)
- # xtdb (4)
Is there any tooling to convert an pom.xml to a deps.edn? 🙂
@d.ian.b Perhaps you can leverage tools deps or tools build itself for this, since I assume it can create a basis from a pom.xml
There’s not really any tool for that although the hard part of reading and understanding the pom is buried in there
@alexmiller You can't do something like (b/basis "pom.xml")
?
Well not that of course, but you could include a local dep to a dir containing a pom
right. and then the basis will contain all kinds of stuff which would let you write a deps.edn from that (with some manual wrangling of course)
You’ll get something useful, but not sure it’s exactly a deps.edn
You also won’t get the mvn/repos out of that as we don’t grab those transitively
Really, you’d only get deps indirectly
But the code will build the pom model, from which you could get anything