Clojurians Log v2

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"

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.

Using cljdoc analyzer seems like the more direct approach.

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)