This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-13
Channels
- # announcements (10)
- # aws (1)
- # babashka (8)
- # babashka-circleci-builds (1)
- # beginners (67)
- # calva (4)
- # cljs-dev (42)
- # clojars (4)
- # clojure (213)
- # clojure-dev (4)
- # clojure-europe (18)
- # clojure-nl (1)
- # clojure-uk (8)
- # clojurescript (13)
- # conjure (6)
- # cursive (63)
- # data-science (5)
- # datomic (11)
- # events (1)
- # graalvm (2)
- # graalvm-mobile (1)
- # honeysql (4)
- # kaocha (3)
- # leiningen (19)
- # lsp (32)
- # malli (3)
- # meander (13)
- # news-and-articles (3)
- # off-topic (8)
- # polylith (5)
- # re-frame (47)
- # reitit (2)
- # shadow-cljs (28)
- # sql (3)
- # tools-build (4)
- # tools-deps (51)
- # uix (9)
- # xtdb (3)
We already use our reverse domain group id on Maven Central for our Java packages, hence we can't claim it on Clojars if my understanding is correct. Given this configuration, is there any chance we can claim something else? foo
instead of com.foo
?
You can verify the same domain with Clojars, you just won't be able to publish an artifact to Clojars that exists on central. For example, if you publish com.foo/bar
to central, you can't publish com.foo/bar
to Clojars, but can deploy com.foo/baz
Oh right, thanks, I misunderstood and thought it was about the group id