This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-05
Channels
- # announcements (7)
- # babashka (61)
- # beginners (146)
- # cider (4)
- # clj-kondo (25)
- # cljsrn (29)
- # clojars (30)
- # clojure (30)
- # clojure-australia (17)
- # clojure-europe (43)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-spec (13)
- # clojure-sweden (7)
- # clojure-uk (8)
- # clojurescript (38)
- # cursive (12)
- # datomic (42)
- # defnpodcast (2)
- # dirac (1)
- # events (5)
- # fulcro (5)
- # graalvm (43)
- # graphql (11)
- # helix (6)
- # jackdaw (13)
- # jobs (4)
- # lambdaisland (8)
- # malli (12)
- # off-topic (83)
- # pathom (9)
- # podcasts-discuss (2)
- # re-frame (6)
- # reagent (3)
- # reitit (8)
- # remote-jobs (1)
- # shadow-cljs (40)
- # vim (21)
I don't like this Clojar policy because it implies that library authors depend on the ownership of a website or an account on Github and/or Gitlab. Website domain names can be lost for a few reasons, so does Github/Gitlab accounts. Technically, the best choice is to use the group-id provided by Clojar and linked to the Clojar account, but it is not very aesthetical.
yup that's exactly right @lee, we already had this happen with Daedalus, and we have some more unreleased libs that will have to get a com.lambdaisland
prefix
are you changing the namespaces to include com
or just the group id in the coordinate?
I don't object to the policy, they do provide multiple ways to establish identity, including clojars itself. I'm all for having globally unambiguous names, I just thought that "lambdaisland" would be unambiguous enough. But I don't feel special enough to ask for an exception.
but this is a package name not an artifact group-id.
you still can have package name lambdaisland.foo
provided by the package org.lambdaisland/foo
for example
same as clojure.core
provided by the package org.clojure/clojure