This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-05
Channels
- # announcements (14)
- # aws (7)
- # babashka (28)
- # beginners (16)
- # calva (2)
- # cider (1)
- # clj-commons (8)
- # clj-kondo (29)
- # clojure (213)
- # clojure-europe (39)
- # clojure-losangeles (2)
- # clojure-norway (9)
- # clojure-spec (2)
- # clojurescript (11)
- # community-development (1)
- # conjure (2)
- # cursive (6)
- # datalevin (2)
- # datomic (8)
- # emacs (29)
- # events (1)
- # fulcro (22)
- # graalvm (14)
- # improve-getting-started (1)
- # jobs (1)
- # lambdaisland (5)
- # leiningen (4)
- # lsp (7)
- # malli (13)
- # meander (11)
- # membrane (13)
- # off-topic (23)
- # polylith (9)
- # re-frame (4)
- # reagent (7)
- # reitit (6)
- # releases (2)
- # sql (58)
- # testing (8)
- # tools-deps (18)
- # web-security (2)
I see that I don’t have permissions to publish potemkin under its original potemkin
clojars group. Are you guys in favor of moving it to org.clj-commons/potemkin
or you prefer I ask Zach for permissions to publish to potemkin
. I prefer moving.
@slipset, my 3 cents: The big benefits of preserving artifact coordinates are:
• continuity for users of the lib
• users can discover updates via tools like antq
• users won’t suffer the chance of clashing nses (for example if both potemkin
and org.clj-commons/potemkin
are on the classpath)
So I think it would be worth asking Zach, and if that doesn’t work out, as a last resort publish to new coords.
I was very happy, for example, when I finally got the rights to reuse existing coords for rewrite-clj.
re your third cent: https://github.com/dm3/clojure.java-time/issues/91#issuecomment-1260106700