This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-15
Channels
- # aws (4)
- # beginners (98)
- # boot (23)
- # cider (63)
- # cljsrn (3)
- # clojure (259)
- # clojure-boston (1)
- # clojure-dev (2)
- # clojure-italy (6)
- # clojure-nl (17)
- # clojure-russia (1)
- # clojure-serbia (1)
- # clojure-spec (36)
- # clojure-uk (74)
- # clojurescript (11)
- # cursive (2)
- # datascript (12)
- # datomic (36)
- # defnpodcast (1)
- # devops (1)
- # docs (1)
- # emacs (15)
- # euroclojure (3)
- # fulcro (13)
- # graphql (1)
- # juxt (2)
- # lumo (27)
- # off-topic (46)
- # onyx (23)
- # pedestal (6)
- # planck (2)
- # portkey (27)
- # re-frame (18)
- # reagent (12)
- # remote-jobs (2)
- # ring-swagger (11)
- # rum (4)
- # shadow-cljs (104)
- # spacemacs (4)
- # sql (3)
- # tools-deps (5)
- # vim (45)
Awesome!
OK, different question: is there any documentation about how to work on a boot extension? Do you just create a namespace in your project and work there? Or would you draft everything in build.boot and then move the code somewhere else?
@ska I often start in build.boot
and then move elsewhere
@ska regarding the license thing: I’m not aware of a boot task for this but you can either a) write one b) generate a project.clj and use lein-licenses
@martinklepsch I already tried variant b which kinda works. I also generated a pom and used the maven report stuff (just run "mvn site") which is massive. I am actually considering writing one myself. I need some time to figure out how to write boot tasks, though.
@ska you could start with something plain clojure that takes a list of deps and returns their license metadata wrapping that in a boot task later will be easy 🙂
Will also study the lein-licenses plugin, maybe the Gradle licenses plugin. Would be awesome to also the the CLJS and JS deps covered.
@ska I’m interested in this too, keep us in the loop as you progress
@ska have fun & feel free to ask anything 🙂
sanity check - I’m working updating some old boot tutorials, and I’m using LATEST in my dependencies in some examples - I did it for reasons I can’t remember, and I usually advocate that people always pin versions - is it beneficial to even tell people that’s a thing?
(boot (show :verify-deps true))
gives me :bad-sig
for all deps except :unsigned
cider nrepl and refactor-nrepl. How does one correct signatures?hey @jjmojojjmojo! nice to see you no here, been too long. i agree re: LATEST, pinning version superior
thanks, I just needed to hear someone else say it lol 😄
@ska pomegranate seems like the thing you want to use, boot notwithstanding. to get data to work with that is
Yeah, I'm wading in pomegranate, boot.aether, boot.pod, lein-licenses and some more. This will take a few days, but just a few minutes ago I got this seq from a test fn: (() nil ("Eclipse Public License") ("Eclipse Public License 1.0") ("Eclipse Public License 1.0") ("Eclipse Public License") ("Eclipse Public License 1.0"))
(first strategy: license tag in POM)
I guess, that's some progress.