Clojurians Log v2

So... there is a pom.xml uploaded to repo, see here: https://repo.clojars.org/miikka/clj-branca/0.1.0/clj-branca-0.1.0.pom

But the corresponding jar file does not contain pom.xml and I believe that's the problem.

That's not said in the docs but I saw some memtion of it in GitHub issues

Heh, now that I have figured tihs out, maybe I'll go to fix Malli...

Or maybe not. Ah well. Maybe I'll document it on the issue tracker of Malli.

I have some time this afternoon to have a stab at fixing that a little bit so pom.xml is less required.

So if I understand correctly, the .pom file in the maven repo is a copy of pom.xml. But cljdoc is relying on the pom.xml in the jar, which some jars don’t include?

the POM is accessible via the repo url and most packaging tools include it inside the jars „META-INF“ directory. In some places we rely on the file being included inside the jar but I’m not 100% sure if that’s a cljdoc thing or a tools.deps thing

tools.deps can fetch deps without it being in the META-INF dir

Tools deps supports adding a jar as a dependency in which case it has(?) to rely on the pom being inside the jar

Yep

I think analysis doesn't need to use that jar though

It would be duplicate work, but it could just use the project instead of the jarpath/pompath.

The other option is to download it and then just assume the location in $M2, checking that out now too.

Maven always downloads the pom, so we wouldn't need to know urls

Oh I see, we also always download the pom. Even less of a problem then :)

In fact, we're already parsing the pom...

For example, this (contains? #{"provided" "system" "test" "compile" "runtime" nil} (:scope %)) will solve the problem where the pom is already used.

But I have a slightly better way too :)

I've opened a PR to fix this :) https://github.com/cljdoc/cljdoc-analyzer/pull/30