This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-21
Channels
- # adventofcode (60)
- # aleph (2)
- # announcements (3)
- # architecture (2)
- # babashka (12)
- # beginners (90)
- # calva (14)
- # cider (32)
- # clj-kondo (1)
- # clj-together (7)
- # cljsrn (4)
- # clojars (10)
- # clojure (161)
- # clojure-dev (110)
- # clojure-europe (58)
- # clojure-nl (3)
- # clojure-spec (35)
- # clojure-taiwan (1)
- # clojure-uk (24)
- # clojuredesign-podcast (3)
- # clojurescript (27)
- # conjure (47)
- # cursive (17)
- # data-science (1)
- # datomic (1)
- # depstar (6)
- # fulcro (20)
- # java (4)
- # jobs-rus (1)
- # luminus (4)
- # malli (10)
- # off-topic (8)
- # re-frame (4)
- # reagent (1)
- # reitit (9)
- # reveal (1)
- # rewrite-clj (8)
- # ring (3)
- # sci (44)
- # shadow-cljs (5)
- # spacemacs (6)
- # specter (8)
- # tools-deps (6)
- # vim (1)
- # xtdb (11)
@alexmiller I'm working on depstar
today and I was wondering how stable the t.d.a API is that underlies the -Spom
option? For ease of use, I've added the ability to override the group/artifact and/or version in the pom.xml
file when building a JAR for deployment and it seemed the most sane approach was to actually update the pom.xml
since it will likely be used in a subsequent deployment step. I know this is sort of complecting two distinct steps but a) it is opt-in and b) allowing the GAV to be overridden without updating pom.xml
seems fraught with potential pitfalls. Having crossed that bridge, I figured it would also be a nice ease of use feature to allow depstar
to run the equivalent of clojure -Spom
for users, since it already has the project basis (now).
Which thing are you asking about specifically?
clojure.tools.deps.alpha.gen.pom/sync-pom
(it's very nice to use, BTW)
Should be relatively stable
Thanks! :thumbsup::skin-tone-2: