This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-21
Channels
- # bangalore-clj (1)
- # beginners (60)
- # boot (30)
- # cider (7)
- # cljs-dev (10)
- # cljsrn (2)
- # clojure (163)
- # clojure-conj (10)
- # clojure-france (1)
- # clojure-greece (2)
- # clojure-italy (7)
- # clojure-russia (41)
- # clojure-serbia (22)
- # clojure-spec (41)
- # clojure-uk (41)
- # clojurescript (178)
- # cursive (36)
- # datascript (1)
- # datomic (23)
- # dirac (38)
- # graphql (12)
- # hoplon (20)
- # immutant (32)
- # instaparse (3)
- # keechma (1)
- # lein-figwheel (18)
- # leiningen (8)
- # liberator (1)
- # luminus (30)
- # lumo (29)
- # off-topic (18)
- # om (17)
- # pedestal (7)
- # planck (37)
- # precept (1)
- # re-frame (67)
- # ring-swagger (2)
- # timbre (1)
- # untangled (8)
- # vim (2)
@micha is boot install
able to install all the jars in the fileset...let's say I have a -sources
and -javadoc
along with the main one...am I supposed to see the all three in .m2
? If yes, then there is a possible bug there 😄
I need classifier
, cool stuff no bug 😄
PR-ed doc and some debug logging
@hiredman after deleting my maven repository and re-installing I got the falling errors in lein deps :tree
:
[org.webjars/webjars-locator-jboss-vfs "0.1.0"] -> [org.webjars/webjars-locator-core "0.30"] -> [org.apache.commons/commons-lang3 "3.1"]
overrides
[ring-webjars "0.2.0"] -> [org.webjars/webjars-locator "0.27"] -> [org.apache.commons/commons-lang3 "3.4"]
@donyorm those two packages (left-most) are both bringing in (transitively) the right-most dependency, & they are different versions.
@dominicm right. I probably should have noticed that. How do I exclude a specific version in boot? And which Ken should I exclude?
[org.webjars/webjars-locator-jboss-vfs "0.1.0" :exclusions [org.apache.commons/commons-lang3]]
@dominicm Just tried exluding from both one at a time. Unfortunately it didn't fix the issue. It's still not finding the org/jboss/vfs/VirtualFileFilter
class under boot
Only lein deps:tree
showed any conflicts. boot show -d
just showed me the tree with now warnings. And yes that was the only conflict I had according to lein.
I got this output from boot show -p
, but I'm not entirely sure how to read it. Are the headers dependencies?
My colleague is asking "`boot -d boot/new new -t app -n` weird... why didn't they make the UX for this as convenient as lein"
@ag it’s not builtin because we wanted to reserve the new
task for user apps
the new
task name, that is
okay. thanks @alandipert
the -d
mechanism might be worth explaining also
novel, in contrast to lein
@donyorm you can’t really know if there’s a problem until you have one, unfortunately
that’s why many users choose to sort out the conflicts even if there are no problems, so that if one arises, and there’s a conflict, it’s probably related
I'm having trouble understanding the output of boot show -p
, is there any part of the documentation that explains it?
I have :source-paths #{"src/clj" "src/cljs" "src/cljc"}
and :resource-paths #{"resources"}
in my build.boot, and apparently that's not okay - I get java.lang.AssertionError: Assert failed: The :source-paths, :resource-paths, and :asset-paths must not overlap. (empty? (set/intersection paths parents))
.
What's the recommended solution for this?
I made boot push
and deploy
more robust and actually now we are Maven Central compatible -> https://github.com/boot-clj/boot/pull/625