This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-25
Channels
- # admin-announcements (18)
- # beginners (16)
- # boot (13)
- # bristol-clojurians (1)
- # cider (41)
- # clojure (116)
- # clojure-berlin (1)
- # clojure-italy (2)
- # clojure-japan (6)
- # clojure-russia (94)
- # clojurescript (46)
- # clojutre (5)
- # core-matrix (2)
- # cursive (1)
- # datascript (14)
- # datomic (10)
- # devops (73)
- # editors (3)
- # emacs (19)
- # hoplon (382)
- # jobs (1)
- # ldnclj (8)
- # ldnproclodo (4)
- # off-topic (50)
- # onyx (3)
- # reagent (2)
- # yada (19)
I have a beginnerish question: I am having trouble with a not-popular library that I want to use very much.
@escherize: Do you have access to the source code?
the good news is I've figured out what I was doing wrong in that instance. But i'm still curious about the optimal approach to investigating external library code
I've found it pretty easy to build from the source code, rename and include the modified version using leiningen
what's the workflow around that, @shaun-mahood ?
Let me just double check and I'll let you know what I did
Using skyscraper as an example, grab the source code and open project.clj. Change defproject skyscraper "0.1.1"
to (defproject skyscraper "0.1.1-mine"
or something else unique. Then do lein install
from within the skyscraper folder and it should install to your local lein repo. You can then refer to it in another lein project.clj by adding [skyscraper "0.1.1-mine"]
as a dependency
Yeah. When I saw you talking about jar files I got kind of scared.
But then I know nothing about java, so jar files are about the scariest part of clojure for me.