This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-09
Channels
- # aws (3)
- # bangalore-clj (3)
- # beginners (40)
- # boot (53)
- # cider (1)
- # cljs-dev (124)
- # cljsrn (22)
- # clojure (105)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-russia (35)
- # clojure-spec (9)
- # clojure-uk (30)
- # clojurebridge (25)
- # clojurescript (107)
- # datomic (18)
- # dirac (21)
- # events (6)
- # hoplon (29)
- # leiningen (5)
- # off-topic (40)
- # om (17)
- # onyx (25)
- # parinfer (2)
- # pedestal (4)
- # perun (2)
- # planck (1)
- # protorepl (6)
- # re-frame (18)
- # reagent (15)
- # ring-swagger (4)
- # specter (2)
- # test-check (7)
- # testing (3)
- # untangled (45)
- # vim (2)
Say I wanted to rename a bunch of standard boot tasks because I wanted to provide an interface that looked a lot like lein’s interface (I know it’s insane, play along 🙂 )… I saw boot.core/rename-task! … anyone seen this in use ?
or zach tellman's potemkin library to map names from boot built-in task namespace into your own task namespace
hey guys, i was wondering if anyone could speak to code sharing between multiple apps with boot… strategies, pain points, etc? I have two apps foo and bar, where bar grew our of foo over a period of time. Foo contains a whole lot of utility code, everything from library wrappers to reusable components. Would it be best to keep foo and bar as “siblings” and have separate boot files/processes? Should there be a third “core” library that the other two require? Any thoughts would be appreciated.
I see.. that’s what I was thinking more or less, its just a bit of work to get everything “libraried” unfortunately
and it feels weird doing so for such a small layer around a few pieces - for example, i wrap reagent with 4-5 helpers
say I had 5 libraries belonging to “core” - would you run with a separate boot file for each one that builds/publishes the lib?
ugh I must be doing something wrong…
(deftask dev
"Build a jar and install to local maven repo."
[]
(comp
(watch)
(build)
(install)))
(task-options!
pom {:project ‘x/my-lib
:version +version+
:url “ "
:scm {:url “}
})
If thats my simple “just build and install locally” boot file; i should be able to either :checkouts '[ [x/my-lib +version+] ]
or use :dependencies
inside another project’s boot file, and boot should check local /.m2 first, right?I must be doing something dumb… like a bad character somewhere. If the ns for my-lib is x.my-lib.core
, I should be able to (:require [x.my-lib.core :as lib])
, but I keep getting a “could not find on classpath” issue