Fork me on GitHub
#tools-deps
<
2021-10-05
>
mokr15:10:07

Hi, just to be 100% certain before I initiate the work: To use :local/root to depend on the source files of a local project, the required project need to have a deps.edn file, right? In other words a the project.clj file of that lein lib is of no use? More specifically I got it to work by adding a deps.edn side-by-side with the project.clj, but I’m not sure if that might have some undesirable side-effect, or if I just missed how to “integrate” with Leiningen.

favila15:10:52

deps or pom are supported

mokr15:10:17

Thanks, I came across that one, but juts wanted to ask in case there was something else that would help.

favila15:10:31

lein can make a pom for you

favila15:10:23

iirc it’s just lein pom

mokr15:10:31

Hmm, I’m not familiar with pom apart from fiddling with it to get a deps project to create an uberjar a while back. How often will it have to be updated? During my experiments yesterday, my main project seemed to hot-reload code when the lib code changed. Will that work if using pom?

mokr15:10:50

I could also just change my libraries to be deps.edn based. I’m just not sure how easy it is to generate and deploy compared to lein.

favila15:10:57

is this a cljs project? hot-reloading should be pretty orthogonal to all this

mokr15:10:34

Yes, my projects are typically Luminus based cljs + re-frame

seancorfield18:10:01

Now that tools.build exists, it's pretty easy to create library and application JAR files for deployment, and it provides a whole toolkit of build-related functions.