Fork me on GitHub
#boot
<
2015-08-28
>
xificurC12:08:36

if boot show -p shows e.g. this for clojure

[?] org.clojure/clojure
    ? 1.8.0-alpha4
      org.clojure/clojure
    ? 1.7.0
      cljs-ajax
      org.clojure/clojurescript
    ? 1.6.0
      reagent
    ? 1.5.1
      compojure
    ? 1.4.0
      org.clojure/core.async
      org.clojure/java.jdbc
    ? 1.3.0
      ring/ring-defaults
    ? 1.2.1
      hiccup
what am I going to get in an uberjar? All of them? Newest?

micha13:08:47

@xifi: if you're making an uberjar you need to have an explicit clojure dependency

xificurC13:08:18

@micha: yeah I mean generally though

xificurC13:08:51

[!] clj-time
    ? 0.9.0
      compojure
    ? 0.6.0
      ring/ring-defaults
    ? 0.5.0
      cljs-ajax

micha13:08:22

are you on windows?

micha13:08:42

lol the unicode characters are not being displayed

micha13:08:06

there should be X's and check marks

xificurC13:08:28

yeah it's a copy-paste from a cygwin terminal

xificurC13:08:41

in cmd or powershell it would look even worse I think

xificurC13:08:04

another fun fact is that when I C-c from a watch task the java process doesn't stop simple_smile

xificurC13:08:46

anyway, what would be the result of uberjaring when show -p shows this? Would all three libs be included? The latest one?

micha13:08:03

no, one of those is checked, and the rest have x's next to them

micha13:08:12

the checked one is the one that will end up in the uberjar

xificurC13:08:22

I (don't) see 😄

micha13:08:34

i guess we should use [+] and [-] maybe instead of ☑️

piyushmandovra16:08:00

guys can you suggest api testing libs from clojure i am using pedestal with friend as web framework and suggestion for unit-testing and datomic query testing

sashton19:08:38

Is it possible to call tasks from within a handler? I'd like to do something like

(deftask foo ""
  []
  (fn [next-handler]
    (fn [fileset]
      (some-task))))
I know what I wrote doesn't work, but is there a way to do that from within a handler? When I tried it, I was getting errors because the task was trying (understably) to parse command line args.

micha21:08:44

(deftask foo
  []
  (some-task))

sashton22:08:17

Can it be done from within a handler middleware?

estsauver22:08:38

So, it seems like boot environ things aren’t passed into the pod in boot-test

estsauver22:08:53

I tried using @martinklepsch ’s suggestion here: https://gist.github.com/2df6cc9d1c007ad7d6de , but those env keys didn’t persist into the test environment.