so if I want to use when or do in a pod, I need to include clojure.core of course right?

and every single symbol will need fully qualified namespace (e.g.: clojure.core/when) ?

@richiardiandrea: clojure.core is referred into all namespaces, in pods too

and the default namespace when you evaluate expressions in a pod is pod

see: https://github.com/boot-clj/boot/blob/master/boot/pod/src/boot/pod.clj#L671-L683

that function prepares a newly constructed pod

it's called when you make a new pod, before the pod is returned

right I forgot that, I split my util -> https://github.com/ScalaConsultants/boot-cljs-src/blob/master/src/replumb/boot/util.clj#L18

maybe I will have a pod-util if it grows too much

the doc string of my util functions states what deps they need

this can evolve in having metadata, :pod-deps for instance, for documentation purposes

those functions that will run in a pod

you can make a separate namespace for them

then just load that namespace, no?

(with-eval-in pod
  (require '[pod-namespace :refer :all])
  ...

yeah, better, I would need to require them in the pod 😄

right, I had not thought about it

that's what i usually do

it is definitely a better solution, and you don't need to fully qualify symbols

right

😄

also you can do things like this

(with-eval-in pod
  (defn f [x] (+ x 100)))

and then later you can do

(with-eval-in pod
  (f 42))

and you get 142

isn't there an implicit do in with-eval-in?

yes there is

yeah you could define f and also call it in the same eval-in

k great

very handy

will try it out

when you do def or defn that persists in the pod

like that defines #'pod/f

understand, great

tnx for the hint

i am going to try in the test too, where I guess it is a bit different there

@seancorfield: good job, boot new works nicely 😄

a question is: does it support + options like: boot -d seancorfield/boot-new new -o . -t tenzing +reagent +divshot +test ?

i'm trying to get my friend's machine to run boot

its a windows machine, but he's using cygwin

there's an error : unable to access jarfile: /usr/local/bin/boot

any ideas?

@richiardiandrea I don't know what those options would do. Feel free to open an issue on GitHub outlining what you'd like to see supported. I'm open to adding any features that folks find useful.

@jethroksy: not sure if Boot supports Cygwin? It's a funky environment. I use Boot on Windows with the plain command prompt and with Git Bash (although the REPL doesn't work in the latter).

yeah he downloaded boot.exe and it just worked

the boot.sh didn't work for him

Ah, yes, that doesn't surprise me. Cygwin isn't really UNIX enough for a lot of things.

a pity 😕

I think it's the worst of both worlds. I recommend GOW - Gnu On Windows - which adds common UNIX utilities to the regular command prompt.

It's not perfect but it's s lot less intrusive than Cygwin.

have you heard of babun?

Nope.

@richiardiandrea: now I see what you're asking, Boot new already supports that.

I thought you were asking for multiple templates (which would also be supported by using new multiple times in the pipeline with the --force option).

@martinklepsch: am I right that with Tenzing you'd say lein new tenzing myapp -- +divshot +test etc? If so @richiardiandrea should be able to do boot new -t tenzing -n myapp -a +divshot -a +test yes?

@seancorfield: good! sorry I did not know let me try

@seancorfield: I tried and replied, still something off I guess, I will check if my setup is good

The extra args worked when I tried the Frege template. Will take a look at Tenzing tomorrow.

yes tomorrow for me as well 😄

I was just setting up our environment on a clean machine and surprisingly I saw many clojure versions being downloaded:

> boot dev
Starting reload server on 
Writing boot_reload.cljs...
2016-01-18 13:24:49.601:INFO::clojure-agent-send-off-pool-0: Logging initialized @6435ms
2016-01-18 13:24:49.646:INFO:oejs.Server:clojure-agent-send-off-pool-0: jetty-9.2.10.v20150310
2016-01-18 13:24:49.679:INFO:oejs.ServerConnector:clojure-agent-send-off-pool-0: Started ServerConnector@34b7309c{HTTP/1.1}{0.0.0.0:3104}
2016-01-18 13:24:49.680:INFO:oejs.Server:clojure-agent-send-off-pool-0: Started @6514ms
Started Jetty on 
Retrieving clojure-1.3.0.jar from 
Retrieving clojure-1.6.0.jar from 
Retrieving clojure-1.6.0.jar from 
Retrieving clojure-1.2.1.jar from 
Retrieving clojure-1.4.0.jar from 
Retrieving clojure-1.5.1.jar from 
Retrieving commons-codec-1.8.jar from 
Retrieving clojure-1.5.1.jar from 
...

i suspect different pods require different versions of clojure, but still it's too many versions, no?

i have [org.clojure/clojure "1.7.0" :scope "provided"] in build.boot though but since it's not a library, i guess shouldn't say :scope "provided"? though technically it's provided by boot, no? it provides the version from boot.properties, no?

@richiardiandrea: I just tried the Tenzing template (we ended up watching TV longer than I expected) and it works fine for me locally so whatever I'm doing with the leiningen-core library in Boot new is breaking on something you have in your ~/.lein/profiles.clj 😞

Oh thanks! no access to my pc now but I will share the file tomorrow, or if there is a way, i will enable debug mode and report

@seancorfield ^

I had a feeling there would be a number of edge cases in Leiningen's behavior that I'd end up having to debug, figure out, and then support somehow

@seancorfield: i'm using boot-expectations, and a single test takes 12s to run on my computer

is this normal?

@jethroksy using watch task I assume?

the assertion itself was 20msec

yeah

Do you have any slow to require namespaces in the test namespace?

how do I profile that

Boot-test uses a fresh pod (Clojure runtime) for every test run and I believe boot-expectations does the same - because of that you might pay for that kind of thing for every run

(There are ways to avoid that)

@jethroksy: in a fresh repl that has not required anything require the namespace and see how look it takes

Maybe time helps

Datomic has been a culprit in that regard previously

interesting

my namespace requires were super fast

0.17msec

Can you paste the complete test ns?

And are you 100% certain that those namespaces haven't been required previously in the repl session? (E.g. Via your init-ns)

yeah functions i defined are inaccessible until my require

I'm not sure what you mean by my test ns

the ones required for my tests to run?

(ns edubot.test-slack-util
  (:require [edubot.slack-util :as sut]
            [expectations :refer [expect]]))

(time (require 'edubot.slack-util))
"Elapsed time: 0.17587 msecs"

(time (require 'seancorfield.boot-expectations) )
"Elapsed time: 0.144637 msecs"

No more like the actual test namespace

Including the tests in it

how would i get that

a little confused ><

Is there a migration guide for the explicit target directory change in the latest boot?

https://github.com/magomimmo/modern-cljs/blob/master/doc/second-edition/tutorial-03.md explains the target task, but I don't see it mentioned in the official docs

Also I'd be interested in an explanation how using comp in build.boot affects the order of execution. Does it matter if target (or other tasks) go at the beginning or end (or middle) of the comp chain?

@pesterhazy: in my understanding, like transducers http://clojure.org/reference/transducers

@pesterhazy: https://github.com/boot-clj/boot/blob/master/boot/core/src/boot/task/built_in.clj#L215-L224 is docs enough, I think. Also available through boot target --help IIRC.

@jaen, I disagree. If people upgrade to latest boot and see a deprecation warning, they should not be required to browse the source to find out what's going on.

I guess what I'm saying is, any reason not to add a note to the wiki about this? (easy to google!)

Well, boot target --help is not source, but other than that I agree - note could say something about doing boot target --help to get an explanation.

actually, I'd strongly prefer a web site somewhere that explains the core tasks

the only place boot tasks are documented right now is in the --help cli, but sometime you can't access that

(e.g. you may have a borken build.boot and boot doesn't start)

That is a good idea, think. It's certainly more handy than navigating to built_in.clj, it usually takes me a while before I remember where the file is in the sources.

I imagine it shouldn't be that hard to write a markdown help generator (so it's always up to date) from the task description and add some preface.

yup

should be automatically generated for sure

@jaen: I also agree with @pesterhazy about an explanation on the tasks order. modern-cljs is for beginners and boot is used only as a build tool, even when it has to explain something more than the official guide to make the things clearer. I remember that while writing the tutorials I had the feeling of adding something on the tasks order more excplicit, but I should have introduce the different behaviour of comp when used with transducers….I could eventually add it, if you think it’s useful. Or you can help in doing that with a PR as well.

also I think it'd be awesome to have a boot guide for the new clojure site

they're accepting PRs now

there's a section for tools (still empty), so boot might be a great candidate

I'm pretty sure it is on the site

http://clojure.org/community/resources

@jaen, there's a "tools" section in the "guides" menu: http://clojure.org/guides/getting_started

Oh, here.

Yeah, it would be neat to get it there then

@magomimmo: my remark wasn't about the task composition though. I was talking about boot tasks description and yes, I agree, a website that syncs to the current built-in task description would be neat.

@jaen: ok. agree as well

@pesterhazy: how about this for a simple example of how boot tasks work?

(defn task-one [next]
  (fn [value]
    (println "before one - " value)
    (let [result (next value)]
      (println "after one - " result)
      result)))

(defn task-two [next]
  (fn [value]
    (println "before two - " value)
    (let [result (next value)]
      (println "after two - " result)
      result)))

(defn task-one-builder []
  task-one)

(defn task-two-builder []
  task-two)

(def task-stack
  (comp (task-one-builder)
        (task-two-builder)))

(defn write-to-disk-or-something [value]
  (println "just doing muh job on - " value)
  {:result value})

(let [pipeline (task-stack write-to-disk-or-something)]
  (pipeline {:some "thing"}))

That is, at least how I understand they work, someone please correct me if that's wrong - it's basically like Ring request cycle - go through all the middlewares and then back again.

@jethroksy: sorry for not replying earlier. I was referring to your test namespace as the file that has the test which is taking a long time to run

@martinklepsch: that would be just the two namespaces i pasted

profiled to total 0.35msec

@pesterhazy: yep. someone should add boot to the clojure getting started guide. I would leave this task to the boot maintainers, because that section is very sensitive

let me try and see if i can replicate that in a small project

@jethroksy: not just the namespace form but the whole file please (if possible)

(ns edubot.test-slack-util
  (:require [edubot.slack-util :as sut]
            [expectations :refer [expect]]))

(expect 1 1)

Oh ok. Have you tried rerunning with the edubot.slack-util dependency removed?

(ns edubot.test-slack-util
  (:require #_[edubot.slack-util :as sut]
            [expectations :refer [expect]]))

(expect 1 1)

Elapsed time: 12sec

@jethroksy: just to double check: you said you're using watch task — is 12s for the first run or every run after a file change?

both

I tried changing the test to fail

the copies are instant I have verbose on true for watch

@martinklepsch: its definitely my project

just created a test project

2s

Starting file watcher (CTRL-C to quit)...

Retrieving tools.reader-0.9.1.jar from 

Ran 1 tests containing 1 assertions in 8 msecs
0 failures, 0 errors.
Implicit target dir is deprecated, please use the target task instead.
Set BOOT_EMIT_TARGET=no to disable implicit target dir.
Elapsed time: 7.488 sec


failure in (test_bar.clj:4) : foo.test-bar
(expect 1 2)

           expected: 1 
                was: 2

Ran 1 tests containing 1 assertions in 16 msecs
1 failures, 0 errors.
clojure.lang.ExceptionInfo: Some tests failed or errored
    data: {:test 1,
           :pass 0,
           :fail 1,
           :error 0,
           :run-time 16,
           :ignored-expectations 0,
           :type :summary}
                          clojure.core/ex-info               core.clj: 4593
seancorfield.boot-expectations/eval90/fn/fn/fn  boot_expectations.clj:   64
          boot.task.built-in/fn/fn/fn/fn/fn/fn           built_in.clj:  264
             boot.task.built-in/fn/fn/fn/fn/fn           built_in.clj:  264
                boot.task.built-in/fn/fn/fn/fn           built_in.clj:  261
                           boot.core/run-tasks               core.clj:  794
                             boot.core/boot/fn               core.clj:  804
           clojure.core/binding-conveyor-fn/fn               core.clj: 1916
                                           ...                             
Elapsed time: 2.437 sec

nvm i'll figure it out. thanks!

How is an easy way to add a TmpDir to a fileset without overwriting already existing entries?

@malesch: you can do it by specifying a :mergers` option you pass to the add-... function

(-> fileset (add-resource tmpdir :mergers [[#".*" boot.pod/first-wins-merger]]))

@micha: Do you have example Dockerfiles for use with boot-beanstalk?

@juhoteperi: i can look for one

i've been using the eb tool lately

Do you copy the repo contents to container and run boot inside container, or copy the artifacts into container?

i usually just run boot in the container as the ENTRYPOINT

so far it's been reliable

But it means that it has to compile Cljs when it starts?

oh, we separate frontend and backend

frontend is static, deployed to s3

Ah right

the containers are a bit slow to start though

not sure if that's just a general beanstalk thing though

@jaen, @pesterhazy there are autogenerated api docs, inluding the built-in tasks here: https://github.com/boot-clj/boot/tree/master/doc

@magomimmo: updated the readme: https://github.com/boot-clj/boot#getting-started

👍

@micha, thanks for adding the link to modern-cljs!

@pesterhazy: see you at ClojureBridge this weekend?

yup

those API docs are terribly useful, @micha, it'd be great if they was a more prominent link, e.g. in the "Tasks" section of the wiki

I'm in the process of writing a guide for perun, maybe you'd like to give it a try at some point

defnitely

it's not obvious that "api docs" include "task descriptions"

@pesterhazy: feel free to edit as you wish

those generated docs will be created for each tagged release, btw

so you can go to any tag and get the docs for that tag in github

@pesterhazy: btw, did you or jelle have a chance to try https://github.com/mjmeintjes/boot-react-native?

yup, I've submitted a few PRs already

https://github.com/mjmeintjes/boot-react-native/issues/13 — "without building a new jar for every change" with boot watch build-jar you can build the jar when things change without needing to do anything

@pesterhazy: ^

the checkouts situation in 2.6.0-SNAPSHOT is better than what is available in 2.5.5 btw

it is (i think) almost identical behavior as when you have the dependency as a jar

(eg, all tasks, even uber and jar work the same, etc)

the contents of the checkout dep jar are not in the fileset with 2.6.0-SNAPSHOT --checkouts option

they're just on the classpath, like with a normal jar

@micha, added a note about API docs here: https://github.com/boot-clj/boot/wiki/Tasks (grey "note" at the top)

added a which can be shown via boot taskname --help bit

👍

@micha Thanks a lot. I will give it a try!

I have a js file that I want to be able to require using :foreign-libs — I’m sure I just have the configuration off a bit, it keeps not working. does anyone have an example project that does this?

is your js file a google closure namespace? like it can be compiled with advanced optimizations right?

oh wait disregard that

lol

ohh was changing the wrong task

the boot-cljsjs task has some things for that if you want: https://github.com/cljsjs/boot-cljsjs/blob/master/src/cljsjs/boot_cljsjs/packaging.clj#L125-L126

woot it works. btw was pretty confusing to have this issue https://github.com/adzerk-oss/boot-cljs/issues/35 closed as “wontfix” — I thought at first there was no way to do it

@jaredly: I think you can also accomplish that with a deps.cljs file in your boot classpath

is Boot expected to load a file named user.clj when I run boot repl?

@samflores: i think that's built into the repl, yes

i mean not boot-related, a general clojure repl thing

user.clj needs to be on the classpath though

when the repl is started

I'm declaring :source-paths #{"src" "dev"} and putting the file in the dev directory. I thought that would be enough.

yes that shold work

can you do (in-ns 'user) in the repl?

or boot repl -n user

that works for me...

the second approach worked, but starting with boot repl and changing to (in-ns 'user) did not

you need to do (require 'user) too

before in-ns

oh, that makes sense 😄

to compile the namespace, yeah

thanks

np!

you can do this, too

(task-options!
  repl {:init-ns 'user})

then that will be the default namespace for repl task

awesome!

Boot new now has support for Boot templates and has app, default, template built-in (`task` is there too but has not yet been worked on so it is broken a.t.m.): boot -d seancorfield/boot-new:0.2.0-SNAPSHOT new -t app -n myapp produces myapp Boot-based project that you can boot run, boot test, and boot build to produce a standalone JAR.

I’ll get task "working" and then cut an 0.2.0 release and gather feedback on what the ideal Boot task template should look like.

Then I’m going to look at https://github.com/weavejester/lein-generate and do something similar for Boot generators and cut an 0.3.0 release.

is util/dbug working generally within with-eval-in ?

I like what you are doing with boot new seancorfield