This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-24
Channels
- # announcements (26)
- # babashka (1)
- # beginners (174)
- # calva (1)
- # cider (10)
- # clj-kondo (27)
- # cljtogether (1)
- # clojars (8)
- # clojure (57)
- # clojure-australia (1)
- # clojure-czech (2)
- # clojure-europe (40)
- # clojure-germany (15)
- # clojure-nl (3)
- # clojure-serbia (6)
- # clojure-uk (11)
- # clojurescript (30)
- # conjure (2)
- # cursive (8)
- # datalog (16)
- # datomic (29)
- # emacs (33)
- # etaoin (1)
- # events (2)
- # fulcro (81)
- # funcool (2)
- # integrant (3)
- # jobs (2)
- # joker (2)
- # kaocha (15)
- # lsp (19)
- # malli (8)
- # membrane (1)
- # off-topic (57)
- # pathom (2)
- # reitit (10)
- # releases (1)
- # remote-jobs (2)
- # reveal (5)
- # shadow-cljs (14)
- # sql (11)
- # tools-deps (8)
- # vim (3)
Are there plans to support custom (not GH) domains as verified group names?
Also, https://github.com/clojars/clojars-web/wiki/Groups should likely be updated as it reads
> Maven Central enforces this as a requirement for publishing there; Clojars does not. If you have a domain name that you control, you can use that as the group ID. Alternatively you can pick a unique, creative name for your project, e.g. korma
, ring
, buddy
.
which, if I am right, is not true anymore due to the Dependency Confusion attack. (I see there is also https://github.com/clojars/clojars-web/wiki/Verified-Group-Names)
Ah, I found the answer:
> If you aren't using one of the auto-verified group names above, you will need to https://github.com/clojars/administration/issues/new?template=group_verification.md with the Clojars staff.
Glad you found the answer! Yes, I need to take a pass at the documentation and clean it up. I hope to get to that this weekend.
@U06SGCEHJ LMK if you want some help with the Clojure CLI / deps.edn
related tooling docs — it’s just Leiningen (and Boot?) right now.
Thanks @U04V70XH6, that would be great. I've never deployed with Clojure CLI
Hi again! Any tips how to troubleshoot
> Could not transfer artifact cz.holyjak:clj-concordion:jar:2.0.0-20210324.173950-1 from/to clojars (https://repo.clojars.org): Failed to transfer file https://repo.clojars.org/cz/holyjak/clj-concordion/2.0.0-SNAPSHOT/clj-concordion-2.0.0-20210324.173950-1.jar with status code 401
? This used to work before, and I have gpg --quiet --batch --decrypt ~/.lein/credentials.clj.gpg
my credeentials
Looking at the logs, it looks like you aren't using a deploy token. You have to use a token in place of a password now. See https://git.io/JfwjM
thx a lot!