This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-26
Channels
- # admin-announcements (33)
- # beginners (41)
- # boot (97)
- # clojure (220)
- # clojure-berlin (3)
- # clojure-russia (31)
- # clojure-sg (3)
- # clojurebridge (2)
- # clojurescript (137)
- # clojutre (13)
- # core-matrix (10)
- # core-typed (1)
- # cursive (18)
- # datascript (1)
- # datomic (93)
- # devops (6)
- # editors (18)
- # emacs (1)
- # funcool (43)
- # hoplon (4)
- # immutant (6)
- # instaparse (3)
- # jobs (25)
- # ldnclj (14)
- # ldnproclodo (4)
- # off-topic (20)
- # om (21)
- # rdf (79)
- # re-frame (14)
- # reagent (12)
- # ring-swagger (18)
- # yada (52)
How do you handle multi-project changes? Using leiningen’s checkouts feature is nice but does not take into account new revisions of dependencies? I find my self continuously lein installing
a SNAPSHOT version of a dependency just to make the depending project pickup the changes.
@ordnungswidrig: that's how I do it
bostonaholic: which is annoying when you have 5 project with 3 level transitive dependencies
yikes
I'm trying to recall how we handled that on a maven project I was on, but that was years ago
probably just wrote a shell script 😜
@ordnungswidrig: I think leiningens "checkout" feature can do that.
@ordnungswidrig: checkouts feature works for me
@ordnungswidrig: don’t forget to add paths to checkouts to your cljs-build config as well
@rauh: I don’t see it using updated dependencies in the „checked out“ project descriptor
@ordnungswidrig: use the checkouts
dir?
Leiningen docs say > If you change the dependencies of a checkout project you will still have to run lein install and restart your repl; it's just that source changes will be picked up immediately.
I just wonder how I can work around that
you could make more checkout directories recursively for the deps of the subprojects too…
@tel I’m not sure about that, I think what is in your top-level checkouts wins on classpath
it just recursively reads the checkout projects as leiningen projects though, right? so if you want to edit the deps of a dep then you should be able to edit the checkout of a checkout
I’d really love to be able to set a set of different environment variables/configuration options on the basis of whether something is dev/test/prod but there doesn’t seem to be anything analogous to the way environ works with lein.
@estsauver: there is environ.boot
I believe
@estsauver: but besides that this may help: https://github.com/boot-clj/boot/wiki/Boot-for-Leiningen-Users#profiles-middleware
@martinklepsch: maybe I should clarify that I mean an environment of something like configuration variables.
It doesn’t seem like changes that are made to variables are persisted throughout the boot process?
How do you mean changes?
@estsauver: if you have any ideas to improve the wiki feel free to do so
I’ll reread the wiki tonight and get back to you. I want to formulate a few questions/specific examples instead of asking very generic questions.
That part didn’t have much to do with pods actually. There’s also always #C053K90BR if you have questions