This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-15
Channels
- # aleph (1)
- # announcements (7)
- # beginners (6)
- # calva (24)
- # cider (18)
- # clj-otel (1)
- # clojars (8)
- # clojure (22)
- # clojure-dev (11)
- # clojure-europe (52)
- # clojure-finland (12)
- # clojure-nl (1)
- # clojure-norway (28)
- # clojure-uk (7)
- # clojured (1)
- # cursive (6)
- # datomic (1)
- # events (1)
- # humbleui (41)
- # hyperfiddle (75)
- # lsp (46)
- # malli (34)
- # matrix (1)
- # off-topic (16)
- # releases (1)
- # shadow-cljs (12)
- # squint (11)
- # timbre (1)
- # tools-deps (24)
How do you get package releases on Clojars to link to Github, both in for the actual release and in the top left link headers? I have the Github URL set as the project's URL in project.clj and use Leiningen to deploy. https://github.com/Sardtok/drift
you can use https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L489-L498 to add <scm> tag into generated pom.xml After deploy it will be picked up by clojars automatically
We have https://github.com/clojars/clojars-web/wiki/About#where-does-clojars-get-vcs-host-information-from in the FAQ, but I just noticed it doesn't have any tooling-specific guidance on how to get those values into the pom. I would welcome updates there.
I wouldn't mind writing up a short guide for Leiningen and deps, but I have I might not be able to do so until Wednesday, as I have a few other things to take care of before then. I have no experience with boot, so can't possibly help out there. I think a link to the FAQ from https://github.com/clojars/clojars-web/wiki/Pushing wouldn't hurt either.
That all sounds great @UUZDC0JMN, thanks! There is no rush at all.
@UUZDC0JMN https://clojure-doc.org/articles/cookbooks/cli_build_projects/#the-generated-pomxml-file talks about how to do this for build.clj
https://github.com/clojars/clojars-web/wiki/About#adding-vcs-host-information-in-leiningen I'll try and find some time tomorrow to add information regarding tools.build.
Looks good, thanks @UUZDC0JMN!