Micha,
2014-11-07 16:25 GMT+01:00 Micha Niskin :
> Oh, I forgot to say, the ^:boot/export-tasks convention makes boot into a
> sort of application container. You can use boot to pull code from the
> internet and run it. This is really nice when combined with Docker, for
> example, but I’m sure we
One thing I forgot to mention is that tasks all agree to not know or care
about where any of these directories are actually located on the
filesystem. Boot provides functions by which the set of files (input or
output) can be obtained. The tasks, when they operate on these files, pay
attention
I'll answer inline below:
On Friday, November 7, 2014 12:15:55 PM UTC-5, Laurent PETIT wrote:
>
> Just to check that I correctly understood the concepts :
>
> - it's upfront, in the task itself, that the decision of whether what the
> task produces is of type "input" or "output".
> - flagging p
Just to check that I correctly understood the concepts :
- it's upfront, in the task itself, that the decision of whether what the
task produces is of type "input" or "output".
- flagging part of its output as "input" type is a way to declare to boot
that the files there MUST be processed further,
Henrik, can you make a github repo with what you were trying to do in your
second question? It would help to be able to see your whole setup.
The add-src task is perhaps confusingly named (Names Are Hard). Its purpose
is to shuffle files around in the file set, moving files that would
normally be
Gotcha! Thanks!
On Friday, November 7, 2014 4:22:35 PM UTC+1, Micha Niskin wrote:
>
> Henrik, the -d option simply adds dependencies to the project. The main
> use case for this option is to pull in dependencies when you have no formal
> “project” and no build.boot file. Mainly it’s used in conc
Oh, I forgot to say, the ^:boot/export-tasks convention makes boot into a
sort of application container. You can use boot to pull code from the
internet and run it. This is really nice when combined with Docker, for
example, but I’m sure we haven’t even found the coolest uses for this yet.
We’re pr
Henrik, the -d option simply adds dependencies to the project. The main use
case for this option is to pull in dependencies when you have no formal
“project” and no build.boot file. Mainly it’s used in concert with the repl
task so you can quickly and easily try something out:
$ boot -d aysylu/loo
Agreed, because it seems like a good tool. :-)
On that vein; what's the syntax for add-src?
I'm trying to include helper.cljs in the project, a file with a bunch of
convenience functions that I use. However, I get the following error:
<< stopping Jetty... >> clojure.lang.Exception
Really looking forward to a couple more blog posts:
- an instructive / provocative one which could be named after "how to
replace leiningen with boot 2". Would be very practical, showing how all
major usecases done with lein translate to boot.
- an tutorial / documenting one on how to write new ta
I tried now, just running boot -u, and it worked perfectly. It's was
probably some caching thing with Clojars. Currently at pre21
Now the command runs without errors, but it also doesn't seem to do all
that much.
Running
> boot -d reagent/reagent:0.4.3
gives the exact same output as running
>
It looks like Clojars is doing what I thought it would do:
https://clojars.org/repo/boot/boot/maven-metadata.xml
2.0.0-pre20
On Thursday, November 6, 2014 5:50:14 PM UTC-5, Henrik Eneroth wrote:
Thanks for looking into it, Micha!
>
>
> I'm getting -pre19 with boot -u, though. Did you forget
Does adding BOOT_CHANNEL=DEV boot -u do the trick? (We aren’t pushing
snapshots currently so it should be the same…in theory.)
On Thursday, November 6, 2014 5:50:14 PM UTC-5, Henrik Eneroth wrote:
Thanks for looking into it, Micha!
>
>
> I'm getting -pre19 with boot -u, though. Did you forget
I don’t understand why Aether isn’t finding -pre20 via the coordinates [boot
"RELEASE"]. I can see the jar file and pom in the repo:
https://clojars.org/repo/boot/boot/2.0.0-pre20/. Do you have any idea why
Pomegranate wouldn’t be fetching that? Is there some subtlety of the
sorting order tha
Thanks for looking into it, Micha!
I'm getting -pre19 with boot -u, though. Did you forget to cut a release or
should I set BOOT_CHANNEL to dev?
On Thursday, November 6, 2014 8:30:55 PM UTC+1, Micha Niskin wrote:
>
> Hi Henrik,
>
> You found a bug! We just fixed it though. Boot was confused b
Hi Henrik,
You found a bug! We just fixed it though. Boot was confused by
`reagent/reagent` when it tried to match that against the artifact ids
returned by Pomegranate, because Pomegranate collapses it to just `reagent`
in that case. If you do `boot -u` you should be updated to boot version
`
Hello Micha!
I'm trying to tuck Reagent in there to take it for a spin, and it seems
reluctant to comply:
boot -d reagent/reagent:0.4.3
java.lang.NullPointerException:
boot.main/dep-ns-decls main.clj: 36
boot.main/export-task-namespaces/fn main.clj: 49
clojure
yes, it's working now, thanks
2014-11-06 0:28 GMT+01:00 Alan Dipert :
> Hi Laurent,
> The boot-cljs-example has started to move ahead of the blog post, and
> includes an optional 'serve' task.
>
> There was a bug in the boot-cljs task that was deleting index.html
> erroneously; I pushed a new ver
Hi Laurent,
The boot-cljs-example has started to move ahead of the blog post, and
includes an optional 'serve' task.
There was a bug in the boot-cljs task that was deleting index.html
erroneously; I pushed a new version and updated boot-cljs-example.
If you `boot -u` to update boot (which was a
Alternatively, if I follow instructions from
https://github.com/adzerk/boot-cljs-example ,
then there's no mention of target/index.html, so I directly jump to
http://localhost:3000/ but I get an HTTP 404, so same problem there I think.
command is different than from the blog post:
$ boot serve -
Thanks Micha for the detailed explanation !
I started following the cljs example, but am stuck right after having
launched the first boot command: I don't see file target/index.html
The command and output look like this (launched from the boot-cljs-example
folder):
$ boot watch speak cljs-repl c
Hi, sorry for the late reply! Boot pretty much takes care of that part for
you, as long as you follow a few basic rules (I will be adding a “how to be
a good citizen of the boot-o-sphere” section to the wiki on github soon):
1.
Tasks don’t fish around in the filesystem directly to find thin
And more seriously, I remember reading that you put an emphasis on removing
the need to use a clean task.
If I'm right, then I'd be interested in knowing how one is encouraged /
helped to pursue this good property in its own tasks ?
Le lundi 3 novembre 2014, Laurent PETIT a écrit :
> Tongue in c
Tongue in cheek question: if Leiningen were the maven of clojure, would you
say boot2 is gradle ? :-)
Le lundi 3 novembre 2014, Micha Niskin a écrit :
> Hi!
>
> Boot (http://github.com/boot-clj/boot) is a build tool for Clojure. We've
> pulled together lessons learned from a year or so using boo
Hi!
Boot (http://github.com/boot-clj/boot) is a build tool for Clojure. We've
pulled together lessons learned from a year or so using boot v1 in
production and are now getting ready to release v2. To show what boot can
do we present a very streamlined and awesome boot-based ClojureScript
devel
25 matches
Mail list logo
