This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-15
Channels
- # adventofcode (46)
- # announcements (3)
- # aws (7)
- # babashka (47)
- # beginners (86)
- # calva (40)
- # cider (8)
- # clj-kondo (22)
- # clojure (63)
- # clojure-europe (16)
- # clojure-hungary (3)
- # clojure-nl (1)
- # clojure-norway (46)
- # clojure-sweden (1)
- # clojure-uk (3)
- # clojuredesign-podcast (2)
- # conjure (4)
- # datalevin (1)
- # events (1)
- # fulcro (5)
- # graalvm (4)
- # honeysql (8)
- # hyperfiddle (15)
- # music (1)
- # off-topic (5)
- # pathom (7)
- # pedestal (1)
- # polylith (3)
- # portal (19)
- # quil (1)
- # re-frame (36)
- # releases (1)
- # specter (3)
- # sql (3)
- # timbre (11)
- # tools-deps (4)
- # xtdb (55)
I'm running into a problem with resolving transitive dependencies that are in a specified :mvn/repos repository. Specifically the case is that some visualization/sketch project depends on quil, and quil depends on jogamp specific dependencies for opengl rendering. I have :mvn/repos {"jogl" {:url "
in the quil deps.edn, and it showed up in the generated pom as a repository. If I do any dependency resolution inside of the quil project, it works, but if I attempt to use quil as a dependency in another project, the jogamp repository does not appear to be transitively propagating for resolution downstream. If I include the mvn/repos override in the downstream project it starts working, but otherwise it tries to fetch the jogamp jars from maven central instead of jogamp.
Is this a problem anyone else has encountered? I assumed the repos definition would propagate transitively, at least based on how maven works, but wasn't sure if that was the case for deps.edn resolvers. It's also possible I have a problem with my jar packaging/pom file, but given it's kind of an edge case it seemed worthwhile to ask about in case someone else had some ideas. Thanks!
this is intentional - from a security point of view we've decided not to include mvn repositories from transitive deps in the parent and you need to re-include at use
Thanks for clarifying, that makes sense. I'll have to think of a workaround, but I'm glad I know it's not from a mistake I made.
Just bumped into this and found answer here. Posted docs issue about it https://github.com/clojure/clojure-site/issues/686.