This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
and it looks to me like lein added into the pom.xml file all the dependencies that existed in :profiles :dev, none of which are actually needed
so now my project is forced to download and use all these old versions that conflict with my project
(set-env! :dependencies '[[some/bad-dependency "1.2.3" :exclusions [some/other-dep some/other-other-dep]]])
here's the library's project file: https://github.com/spellhouse/phalanges/blob/master/project.clj
@micha: I don't feel like I should have to work around this other library's requirements
phalanges is just a simple cljs library - it shouldn't be requiring all that other stuff
I guess what I don't understand it this. I've been working on this code for days with no problems. Now I added phalanges and suddenly when I compile I see old versions of lots of libraries being downloaded from clojars and my compile fails.
I just deleted my entire local maven repo, compiled poly with the phalanges dependency, compiled my app, same error
but i don't see what the problem could be because the 1.6.0 release has only one dependency as far as i can see in the pom, a dep on org.clojure/clojure
for poly it is small:
[!] org.clojure/clojure ? 1.5.1 spellhouse/phalanges ? 1.4.0 org.clojure/core.async
the deps under the version are the depenedncies of your project that pull that version in transitively
that's why I found it so frustrating - its complecting the library with the developer's work environment
or, yeah, a lein bug that it puts those dev profile dependencies into the pom.xml as regular deps
testing key events in the browser is fun, especially when you hit the wrong keys and close the browser...