This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-28
Channels
- # aws (1)
- # babashka (113)
- # beginners (41)
- # cider (9)
- # cljdoc (15)
- # cljs-dev (8)
- # cljsrn (5)
- # clojure (113)
- # clojure-australia (4)
- # clojure-europe (40)
- # clojure-nl (8)
- # clojure-taiwan (1)
- # clojure-uk (60)
- # clojurescript (59)
- # code-reviews (2)
- # conjure (1)
- # datahike (12)
- # events (1)
- # jobs (1)
- # kaocha (4)
- # lsp (24)
- # luminus (19)
- # malli (4)
- # off-topic (28)
- # pathom (10)
- # philosophy (1)
- # portal (6)
- # re-frame (3)
- # reagent (9)
- # remote-jobs (1)
- # shadow-cljs (31)
- # sql (24)
- # tools-deps (6)
- # xtdb (14)
If I have the app jar, what is the CLI to run the analyzer on that?
@holyjak There’s a few ways documented here: https://github.com/cljdoc/cljdoc-analyzer#usage:
clojure -m cljdoc-analyzer.main analyze \
--project io.aviso/pretty --version "0.1.29" \
--output-filename "io-aviso-pretty-0.1.29.edn"
@holyjak did you have success integrating this into your CI btw? would be a nice thing for us to document if it’s not too complicated
Throwing another idea as I think of it: There is also cljdoc ingest
which in turn calls cljdoc analyzer… and we have https://github.com/cljdoc/cljdoc/blob/master/doc/running-cljdoc-locally.adoc#run-cljdoc-locally-from-docker… but I am not sure if this would work well from CI.
That way we could cover even more stuff
It would be cool to deploy cljdoc-analyzer (and cljdoc itself) to Clojars. They both use deps.edn
…. I was just gonna ask how to do this best but now I’ve actually found this tool which looks like it might be a pretty good solution: https://github.com/applied-science/deps-library#usage
I use deps-deploy
Ah, I see deps-library composes deps-deploy with depstar
I approve
It uses a super-old version of depstar
— lots of bugs fixed since then.
I would recommend just using depstar
and deps-deploy
“manually”, i.e., separately, and using up-to-date versions of both.
(the depstar
readme has a section that talks about my deployment process which uses aliases for depstar
and deps-deploy
)
@seancorfield for some reason I really don’t like having the pom.xml in there as a file that is 90% information from elsewhere (i.e. deps from deps.edn)