Fork me on GitHub
#boot
<
2017-02-24
>
cpmcdaniel01:02:18

hmm, how would I add local artifact dependencies in boot?

pesterhazy01:02:30

can't you install the local artifact?

cpmcdaniel01:02:39

I think better

cpmcdaniel01:02:48

I have a git clone of the project

cpmcdaniel01:02:14

I can add a :resource to point to its <project>/target/classes directory

pesterhazy01:02:47

seems dangerous

dominicm09:02:24

@cpmcdaniel I think there's a checkouts feature in boot you may be interested in?

cpmcdaniel12:02:03

actually, I needed the other project’s dependencies as well

cpmcdaniel12:02:31

fortunately(?) it was a maven project, so a local install did the trick

cpmcdaniel12:02:41

on a different topic...

cpmcdaniel12:02:05

I suppose the clojure dependency has to be explicit if you expect it to be included in an uber jar?

mateusz.fiolka12:02:06

Hi, boot allows me to write "one file" executable clojure programs (thanks to shebang boot and (set-env! :dependencies). However .. is there a way to hook emacs cider as a repl to such program?

cpmcdaniel12:02:53

you can add a dependency on tools.nrepl and start a repl from within your program

cpmcdaniel12:02:05

or you might have access to boot’s own repl task

cpmcdaniel12:02:11

it’s just a function

mateusz.fiolka12:02:21

@cpmcdaniel It requires mofiying the code to work in two modes though (normall running and running a repl). That's a solution, but maybe there's a way to avoid that?

mateusz.fiolka12:02:18

Ok, I guess I can just run a boot repl, hook into it and then evaluate the whole file in t.

flyboarder17:02:25

^updated to 1.4.3 now provides option to include version file or generate version namespace for use by applications

richiardiandrea17:02:58

the option for :develop just makes a lot of sense!

flyboarder17:02:06

@richiardiandrea that is technically a breaking change, :no-update was renamed to :develop, hope it help's everyone out tho!

flyboarder17:02:35

Readme now updated with new examples as well 🙂

alandipert20:02:12

@adamfrey recently hit a problem with clj-http, strange exception, in trying to fix it i ran across a bug report of yours elsewhere. maybe a clj-http ticket?

adamfrey20:02:40

do you have the link to the bug report?

alandipert20:02:52

no, but i figured out the problem

alandipert20:02:54

wasn't sure you ever did

adamfrey20:02:12

I can’t remember, so let’s assume no

adamfrey20:02:39

what was it?

alandipert20:02:06

the problem is with potemkin

alandipert20:02:27

clj-http depends on a recent potemkin, that's 1.8 compat

alandipert20:02:38

but another library of yours was probably also bringing in potemkin, an older non 1.8-compat version

alandipert20:02:56

maven was selecting the older, non 1.8-compat version, which blows up clj-http

adamfrey21:02:12

interesting. Yeah, I’ve avoided that error since. Thanks for the report! Very thoughtful of you