This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-23
Channels
- # babashka (22)
- # beginners (8)
- # calva (7)
- # clj-kondo (65)
- # cljdoc (9)
- # cljsrn (1)
- # clojure (53)
- # clojure-australia (4)
- # clojure-europe (49)
- # clojure-gamedev (2)
- # clojure-italy (13)
- # clojure-nl (1)
- # clojure-spec (19)
- # clojure-uk (4)
- # clojurescript (48)
- # clojureverse-ops (1)
- # core-async (3)
- # css (2)
- # cursive (15)
- # datomic (6)
- # degree9 (2)
- # depstar (4)
- # emacs (2)
- # find-my-lib (1)
- # fulcro (16)
- # graalvm (11)
- # gratitude (1)
- # honeysql (9)
- # introduce-yourself (2)
- # jobs (1)
- # joker (2)
- # livestream (2)
- # malli (16)
- # nbb (4)
- # news-and-articles (2)
- # off-topic (1)
- # pathom (7)
- # polylith (10)
- # practicalli (1)
- # re-frame (7)
- # reitit (1)
- # releases (3)
- # remote-jobs (1)
- # rewrite-clj (19)
- # shadow-cljs (10)
- # tools-build (1)
- # tools-deps (9)
- # uncomplicate (1)
- # vim (3)
- # xtdb (44)
I’ve got an issue for the keycloak-clojure
library that include a dependency in the namespaces displayed on cljdoc (cli-matic for instance), see https://cljdoc.org/d/keycloak-clojure/keycloak-clojure/1.17.9/doc/readme
I tried to add the :scope "provided"
to exclude the dep from being analyzed but without success.
Maybe that’s because the dep is included as a git url and not as maven?
cli-matic/cli-matic {:git/url ""
:sha "3e072260e359be51bf6646e219042c319dd9f5f8"
:exclusions [expound/expound]
:scope "provided"}
Hey! :) Can you check if your jar contains Cli-mastic source files?
Yeah bingo! that’s it, the problem is then upstream in the jar building process (I use depstar).
Actually depstar has an option :paths-only
that do not treat :local/root
and :git/url
as providing source dependencies in deps.edn
. Adding that option to my build alias solve the problem
https://cljdoc.org/d/com.github.seancorfield/depstar/2.1.278/doc/all-the-options
Glad it helped and thanks for the kind words 🙂