This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-22
Channels
- # announcements (21)
- # aws (7)
- # beginners (105)
- # berlin (1)
- # calva (14)
- # cider (20)
- # clj-kondo (62)
- # cljdoc (7)
- # cljsrn (1)
- # clojure (206)
- # clojure-dev (2)
- # clojure-europe (11)
- # clojure-france (2)
- # clojure-italy (2)
- # clojure-nl (1)
- # clojure-uk (34)
- # clojured (1)
- # clojurescript (52)
- # copenhagen-clojurians (2)
- # core-async (1)
- # cryogen (3)
- # cursive (36)
- # data-science (27)
- # datomic (48)
- # emacs (1)
- # events (1)
- # fulcro (27)
- # hoplon (51)
- # jobs-discuss (1)
- # leiningen (1)
- # nrepl (2)
- # off-topic (52)
- # pathom (43)
- # quil (10)
- # re-frame (11)
- # reitit (28)
- # remote-jobs (2)
- # shadow-cljs (36)
- # sql (12)
- # tools-deps (7)
- # vim (32)
- # xtdb (17)
when I jarsign the .jar containing dependency on crux, then jarsigner fails as it spots duplicate (actually triplicate) entry of project.clj in final jar... so I assume one coming from clojure, other from taonesso... Question - is project.clj needed/used during actual runtime?
Hi @olekss.janis! Welcome back 🙂 project.clj shouldn’t be required at runtime, so you can get omit it from a jar. We should omit it as well, good spot.
ok... btw, what evil would happen if you would aot your stuff? your previous fix fixed our problem, but still startup for first time is kinda slow... would aot fix it and wouldn't it break something necessary ? (this is not requirement, just curious)
Not sure if aot would help. aot could lead into in class version conflicts between different crux modules, or if you or one your dependencies will use the same library as crux.
my solution to project.clj during signing is to have this section at the build.gradle of the module containing the crux dependency (and one being signed over) jar { exclude("project.clj") }
You might be able to aot yourself with gradle plugin
another question -> if I have jdbc connection, can I pass/inject it into crux to use, as we would like to have crux piggyback on our transaction
hi @olekss.janis - the current JDBC implementation uses https://github.com/seancorfield/next-jdbc, it uses this library to get a Datasource
that is used for subsequent options. Your current options would be to provide your own crux.db.TxLog
to override the JdbcTxLog
that is used and delegate accordingly, or hook into next-jdbc somehow