This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-21
Channels
- # 100-days-of-code (6)
- # aleph (26)
- # beginners (129)
- # boot (5)
- # calva (3)
- # cider (5)
- # cljs-dev (16)
- # cljsrn (4)
- # clojure (204)
- # clojure-dev (36)
- # clojure-italy (23)
- # clojure-nl (4)
- # clojure-spec (221)
- # clojure-uk (60)
- # clojurescript (68)
- # datomic (47)
- # emacs (4)
- # figwheel-main (50)
- # fulcro (29)
- # graphql (10)
- # hyperfiddle (19)
- # lein-figwheel (3)
- # leiningen (20)
- # liberator (3)
- # off-topic (89)
- # onyx (15)
- # pedestal (1)
- # portkey (2)
- # re-frame (3)
- # reagent (6)
- # ring-swagger (1)
- # rum (12)
- # shadow-cljs (10)
- # uncomplicate (4)
- # vim (5)
Hello folks! Could somebody kindly advise me how to debug a lein plugin? I have added lein cooper to my project but it fails with an excepion. Is setting LEIN_JVM_OPTS to -Xdebug -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y
the way to go? Thanks!
Also, what is a good way to use my clone of a plugin (preferably without needing to install it to my local mvn repo, use it directly from its git clone directory)? Thanks!
lein
will use the DEBUG
flag to enable debug level logging. if the plugin is well-written, it’ll use the logging utils that respect that
as far as using your own clone of a repo, why not install the snapshot and reference the snapshot version you installed?
Not sure of a better way. I don’t know that lein
checkouts feature works for plugins (could be proven wrong there)
you can even change the version to like plugin-name-MINE-SNAPSHOT
if you don’t want to collide with the “real one”
thx but DEBUG=true is not enough, I need a true debugger
then:
(require '[leiningen.core.project :as p])
(def project (p/read "path/to/your-own/project.clj"))