Is there a recommended REPL-driven workflow to use when creating a task?

I'd like to be able to trigger a task and inspect the output. Perhaps I'm overthinking this...

@domkm: I usually do load-file on build.boot but with core/pod etc referred explicitly. Then I move it to a different file

I bet we could have a slicker workflow with some more thought tho

@alandipert: I don't think I quite follow. I'd like to be able to def a task, then invoke it with a fresh fileset from the project (IDK how to create this), and then inspect the output of the task (a modified fileset, I presume).

With that said, I got this task to work so I don't need the above workflow right now, but I'd certainly like to have it figured out for future reference.

@domkm: what i meant was i'll open a boot repl and after i modify my build.boot i (load-file "build.boot") in the repl. then at the repl i invoke (boot (my-task)) to see what it does

maybe what would be cool is an emacs minor mode that does (load-file "build.boot") as an after-save action on build.boot files, if there's an active cider connection to the same project

or a boot task that watches build.boot and reloads it?

Ah, I see. Thanks @alandipert

@smw: that would be cool too. we need metaboot

@cfleming: i emitted some possibly weird and incoherent thoughts on the reddit thread about boot/cursive integration, very interested to hear what you think

@alandipert: Thanks, will take a look

Seems like a pretty good idea, make it the build tool’s responsibility to inform cursive/other editors.

Some responses back on reddit

I have a pretty good idea about how boot works, but I haven’t spent enough time seeing how most people actually use it in practice. I’ll need to actually spend some time doing that to get an idea of the best approach.

one in-practice example i deal with daily is the case of the uberwar

in a servlet container boot isn't the entrypoint, so there aren't pods at servlet time

(i want to change this in the future but that's where it stands now)

I know seancorfield mentioned at some point that they have all their dependencies externalised into an EDN file - realistically I’ll never be able to support that.

so, like anyone preparing an uberwar, i need to deal with conflicts etc in the packaged jars, mergers, etc

Ok, so a lot of the dependency management is done by hand?

not a lot, just the usual

same as one would do in maven or gradle

vs. what i can do at build time, where i have pods

Do you have a public example of a task doing this that I can look at?

hm, let me liberate some IP

1sec

https://gist.github.com/alandipert/90640f35771aa44cae5c

that's maybe the trickiest dependency thing i've ever done in an actual work app

the ~boot-version business

hoenir.main there is https://gist.github.com/alandipert/393c8709708cdf06e655

this app is an executable uberjar

so all the deps except expectations makes it into the jar, because it's :scope "test"

So I can probably handle all that except the boot/pod dep

Sorry, I’m trying to get a release out the door, I’ll have to pick this up later

But I’m interested in examples of funkiness, although in my experience the best way to get those examples is to release something which doesn’t support them

no prob. i updated the build.boot with kinda what i was imaginating

Yeah, I see. I still have the problem that that will only support boot projects specifically designed to be used with Cursive

not necessarily, for instance users could instrument set-env! in ther profile.boot, which is code that runs before build.boot

but yeah the static analysis maybe gets you as far as you need to go with your users, i don't know

anyway thanks for checking it out, gonna head out myself! good luck on release

We actually have some dependency versions in a properties file and we use that to post-process the EDN and then we sometimes we pour additional deps into that. So our dependencies are completely dynamic.

We also have a few places where use "RELEASE" instead of a specific version.

(For tooling, not for our actual programs, and that's mostly tooling we control).

So, no chance that any IDE could figure out this, short of running boot show -c ... which, funnily enough, is exactly how we bootstrap our hybrid web application.

@seancorfield: curious, why RELEASE and not a version?

oh nvm read next msg - i can see how it makes sense if you own the artifact

Because then we don't have to update certain dependencies in our tool chain: we can just publish a new version of a tool and everything picks it up on the next restart.

It's also great while we're prototyping and developing new pieces (so lazy). But since we can then peg versions in a properties file later, we can override RELEASE.

Boot has allowed us so much control over stuff that was painful with Leiningen.

amen

yeah i live in a boot bubble

but i have a sense that boot's merits make the most sense to people when it's used on a team, to define an organization's workflow

maybe it's that tools don't matter if you use them alone, or something

@cfleming: we keep maintaining a project.clj and a build.boot in tandem, just so cursive can consistently format our code 😕 i keep symlinking our build.boot under src and adding a (require '[boot.core :refer :all]) at the very top, so deftask, set-env! and task-options! are resolvable. but it's still not enough, because boot.core is an implicit dependency for build.boot, so i have to add [boot/core "2.5.5"] to the project.clj i generated with lein-generate (from https://github.com/boot-clj/boot/wiki/For-Cursive-Users)

but then i have the boot version specified in 2 unconnected places: boot.properties and project.clj, so they can diverge 😞

@onetom: Yeah, I know this is painful. I’m definitely planning to do what I can.

@cfleming: we do love Cursive otherwise! we - from Exicon - bought a few licenses in 2 rounds, so all of our pairing workstations are equipped with Cursive now. thanks a lot for the great software. we learnt so much about clojure and clojure libs thanks to Cmd-Y and F1

so it still worth all that extra hassle

been playing around with Boot and I like it a lot so I’m going to be using it for my next project! But one thing seems vague to me. I’m building an ring API server and most things I’ve seen with boot like pandeiro/boot-http are meant for frontend dev just to serve static contents. Is there a lein-ring style task out there or would you create your own deftask to call my own -main or handler function?

@kingoftheknoll: the server task does have a handler option where you can pass a custom handler

in general boot task-name --help is often a good place look for this kind of stuff

you’ll have to forgive me I don’t see a built

in server task

or any other than pandeiro/boot-http in the third party tasks listed.

Sorry I see that pandeiro/boot-http has a handler option

ah, I meant serve task of course

and yes, the one in pandeiro/boot-http @kingoftheknoll

thanks, I’ll give that a try 😃

I'm writing a shebang boot script and am getting errors. The problem is that boot reports something like the following: clojure.lang.ExceptionInfo: Unable to resolve symbol: o in this context data: {:file "/tmp/boot.user5782324653526199192.clj", :line 17} java.lang.RuntimeException: Unable to resolve symbol: o in this context It's obviously a syntax error, but the larger problem is my inability to access /tmp/boot.user5782324653526199192.clj after execution ends and the reported line number in my source file contains no errors. Is there any way to remedy this? Thanks...

@inhortte: you can try using boot -b which will print the generated boot script

@martinklepsch: How do I place options to boot in the shebang? #!/usr/bin/env boot -b does not work.... (and I see there are pages and pages of discussion on this at stackoverflow ).

@inhortte: I think just running boot -b file might be equivalent?

regardless of any errors, the output is the following:

(ns boot.user (:use boot.core boot.util boot.task.built-in))

(clojure.core/comment "start boot script")

(clojure.core/comment "end boot script")

(clojure.core/let [boot?__1228__auto__ true] (clojure.core/if-not boot?__1228__auto__ (clojure.core/when-let [main__1229__auto__ (clojure.core/resolve (quote boot.user/-main))] (main__1229__auto__ "pdir_diff.clj")) (boot.core/boot "pdir_diff.clj")))

`

@martinklepsch: I got it working!

Question, once you start watching stuff you lose the repl prompt, how do you get it back?

ahhh, C-c

@kingoftheknoll: I usually have a terminal boot dev with the watch running and then connect to the REPL server

hello everyone

is there some workaround for the java.nio.file.AccessDeniedException on Windows 7?

trying to do the modern-cljs tutorials, and don't really want to install Linux for this... 😞

Is there any way to compose the repl client with other tasks? I'm trying to figure out magic.

@dimovich: You might need to try to isolate the cause

@dimovich: i'm not aware of anyone running without those errors on win7.... but i do see frequent reports that everything works great on win 10

@inhortte: there are limitations with the shebang method in Unix

Anyone got an example of how to handle scss compilation? After some playing around I can compile scss from src/styles to /target/public/styles. But I’m lost in how to get the produced css into the uberjar. Not even sure if the scss files should live in a source-paths dir. Realise that I sound confused. But anypointers where I can try and read up on this stuff?

@micha it's possible to include one option (or argument) meaning none if i use /usr/bin/env ...

Ok think I got the sass routine working (might just have freaked out since I had to deal with the classpath).

@micha: You had any more thoughts on your isolated repl middleware into pod stuff?

@dominicm: i remember spending some time trying to make it work when we first were thinking about how to make the repl task, but i didn't make much progress at all

the essential problem is that the nrepl machinery calls eval directly

so nrepl itself can't be in an isolated pod

what i wanted to do was have it instead send a message to a socket repl server instead

Yeah. Hmm..

I mean, MrAnderson works for most things anyway I guess.

Remember when we used to be normal?

ah normal