This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-02
Channels
- # announcements (1)
- # architecture (1)
- # aws (21)
- # babashka (37)
- # beginners (173)
- # boot (12)
- # chlorine-clover (5)
- # cider (36)
- # clara (11)
- # clj-kondo (25)
- # clojure (128)
- # clojure-europe (7)
- # clojure-finland (3)
- # clojure-germany (2)
- # clojure-nl (57)
- # clojure-uk (23)
- # clojurescript (71)
- # clojurex (1)
- # core-async (30)
- # core-typed (5)
- # cursive (35)
- # datomic (8)
- # duct (4)
- # emacs (8)
- # exercism (41)
- # fulcro (116)
- # jackdaw (4)
- # jobs-discuss (6)
- # juxt (4)
- # kaocha (16)
- # leiningen (14)
- # malli (5)
- # observability (4)
- # off-topic (2)
- # pathom (19)
- # pedestal (29)
- # re-frame (64)
- # reitit (18)
- # ring (8)
- # shadow-cljs (3)
- # sql (13)
- # tools-deps (32)
- # tree-sitter (5)
- # yada (17)
@dominicm @mccraigmccraig This was part of my learning about yada
and how to use it to serve resources. just a few basic resources of different types i.e. As part of that excercise, i wanted to add a clojurescript
frontend and added clojurescript
and shadow-cljs
as a dependency. That's when it started giving the error. If I commented out shadow-cljs
, the error went away. I did use lein deps :tree
and tools.deps clj -Stree
, but I couldn't figure out from the output, a way to resolve this. But adding clj-time
as a dependency stopped the error.
sounds like you were in jar-hell @dionysius.almeida - the way out usually involves adding explicit deps and excluding some implicit deps
with lein i find it helpful to use :pedantic? :abort
, which forces you to consider every transitive dep conflict explicitly, or it errors
i don't know if there's an equivalent deps.edn construct
@mccraigmccraig Yeah..learn't something new i guess. Also, including :pedantic? :abort
caused each run to suggest more exclusions ..and it kept going on, so I gave up on it. Since I consider myself a beginner to clojure, this is not something I would want to spend time looking into. For now, if I encounter any such errors, I understand that adding an explicit dependency this the way to go. Cheers 🙂
i seem to recall reading that deps had a saner conflict resolution by default
I think what's more likely is that clj-time was coming in by accident, and being used.
Then in an updated version of whatever brought in clj-time, no longer brought it in.
I read somewhere that deps
resorts to newest version while lein
resolves to older version..not sure if this is true
@dominicm not sure what you mean ? It's being used by yada/cookies.clj
..isn't that how it's being included ?
ah, yeah, probably true
@dionysius.almeida in that case I'd love to see your deps edn, and I should double check that yada behaves here
Here's my deps.edn
, nothing special. This is after adding clj-time
{:paths ["src/clj" "src/cljs" "resources"]
:deps {org.clojure/clojure {:mvn/version "1.10.0"}
yada {:mvn/version "1.4.0-alpha1"}
integrant {:mvn/version "0.8.0"}
prismatic/schema {:mvn/version "1.1.12"}
clj-http {:mvn/version "3.10.0"}
com.cognitect/transit-clj {:mvn/version "1.0.324"}
org.clojure/test.check {:mvn/version "1.0.0"}
com.taoensso/timbre {:mvn/version "4.10.0"}
clj-time {:mvn/version "0.15.2"}
com.fzakaria/slf4j-timbre {:mvn/version "0.3.19"} ;; To log slf4j to timbre
}
:aliases
{:dev {:extra-paths ["dev"]
:extra-deps {org.clojure/clojurescript {:mvn/version "1.10.520"}
thheller/shadow-cljs {:mvn/version "2.8.92"}
binaryage/devtools {:mvn/version "0.9.10"}
org.clojure/tools.namespace {:mvn/version "1.0.0"}
keechma {:mvn/version "0.3.5"}
}
}}
}
That's great, thanks. I'll have a little poke at the before after tree, but this seems to be a yada bug.
@dominicm thanks 👍:skin-tone-3: