This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-03
Channels
- # announcements (5)
- # babashka (8)
- # beginners (98)
- # biff (2)
- # calva (20)
- # cider (16)
- # clerk (2)
- # clj-kondo (20)
- # cljdoc (19)
- # clojure (90)
- # clojure-art (3)
- # clojure-boston (1)
- # clojure-europe (7)
- # clojure-nl (2)
- # clojure-norway (47)
- # clojure-uk (3)
- # clojurescript (10)
- # cursive (10)
- # data-science (1)
- # datalevin (1)
- # defnpodcast (1)
- # events (2)
- # fulcro (11)
- # gratitude (2)
- # honeysql (18)
- # hyperfiddle (11)
- # introduce-yourself (1)
- # jobs (2)
- # lambdaisland (4)
- # lsp (6)
- # malli (4)
- # membrane (3)
- # off-topic (58)
- # polylith (14)
- # portal (2)
- # releases (2)
- # ring-swagger (4)
- # tools-deps (8)
- # xtdb (8)
Trying to understand why this build fails, is there a problem with git dependencies? https://app.circleci.com/pipelines/github/cljdoc/builder/50687/workflows/e0c33864-6dae-4c12-9dbb-ec08e7bfc235/jobs/67062 Project: https://github.com/bsless/aero.extensions
Hi Ben! cljdoc downloads your jar from Clojars and resolves dependencies as per pom.xml
Looking at the logs it looks like it can't find the aero.alpha.core
namespace. I think this is because you depend on it only in deps.edn
and not in pom.xml
If you update the pom.xml
to contain the respective dependency it should work. That does require the dependency to be available in a Maven repo though.
Hope that helps / will work for you. It would be nice to fully support deps.edn
but given that API docs on cljdoc are always versioned its a bit complicated
I assume I'd have to not just update my pom but use a mvn version for aero as well?
deps.edn
doesn't have a version / is usually used via git so it's not "tagged" in a sense. Everything in cljdoc is tagged to a version. Does that make more sense? I'm a bit tired so maybe this explanation isn't the best 😁
And yeah you'd have to use a maven version of aero as well as you can't specify git coordinates in pom.xml
fwiw, we did a bunch of thinking for supporting libs from sources https://github.com/cljdoc/cljdoc/issues/459
Seems like it doesn't cover clojars published libs with git dependencies then. It's not critical, thanks anyway 🙂
I’m probably missing some detail of what you are doing (or maybe have not had enough coffee yet!) but clojars is maven based and works with jars and poms. I do have a foggy memory of the now deprecated depstar bringing source code from git dep sources into the jars it built… are you using depstar to build your jar?
No, but it's probably a bad idea to use a git dep in a library then publish to clojars.