Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2017-10-06

Channels

#boot
<
2017-10-06
>
ag21:10:38

if I update jar locally (for testing) and then in the app that I'm using that package, do I have to restart the repl or it's enough to re-evaluate (set-env! ... ?

dominicm22:10:39

@ag Turn on checkouts for that jar, probably after restarting :)

ag22:10:42

I don't know what that means

dave00:10:49

i don't think i understand what checkouts give you over just running lein install (or boot build-jar install or whatever) in the project you're depending on / developing

dave00:10:07

that's typically what i do, and it seems to work the way i've heard checkouts described

danielcompton00:10:33

This does it automatically

danielcompton00:10:36

whenever you make changes

dave00:10:14

oh, i see

dave00:10:01

so it's like adding a watch on that project in your local maven repo, in addition to the fileset of the bigger project

danielcompton00:10:32

Lein ones are source based, whereas boot ones just reinstall the JAR into your ~/.m2 and the boot watcher picks up the change

danielcompton00:10:42

(At least i think that's what the boot one does)

dave00:10:16

cool! i'll have to try that the next time i run into this kind of situation

flyboarder19:10:44

NOTE: checkouts only works in the root of a project, you can’t wrap it in a task, or anything else, it won’t pickup the changes otherwise

phreed23:10:16

When I have an error in my build.boot it misreports the line number. This is because the file that is actually processed has some extra lines at the top as can be seen by boot -b . It just makes me do a little more work to track down the problem.