This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-26
Channels
- # admin-announcements (4)
- # beginners (3)
- # boot (78)
- # cider (13)
- # cljs-dev (29)
- # cljs-edn (8)
- # cljsjs (11)
- # cljsrn (15)
- # clojure (81)
- # clojure-beijing (2)
- # clojure-belgium (3)
- # clojure-canada (1)
- # clojure-dusseldorf (8)
- # clojure-greece (6)
- # clojure-russia (40)
- # clojure-sg (1)
- # clojure-uk (59)
- # clojurebridge (1)
- # clojurescript (101)
- # core-logic (1)
- # cursive (3)
- # data-science (1)
- # datomic (60)
- # emacs (4)
- # error-message-catalog (12)
- # funcool (1)
- # hoplon (60)
- # jobs (1)
- # jobs-discuss (40)
- # leiningen (5)
- # liberator (1)
- # mount (22)
- # off-topic (8)
- # om (16)
- # onyx (53)
- # re-frame (11)
- # reagent (2)
- # specter (4)
- # testing (18)
- # untangled (51)
I said this on #C03S1KBA2, but it’s probably relevant here too:
What do people think about disabling signing of JARs when deploying, at least to Clojars? In my experience it is a *significant* barrier to entry for newcomers, and I’m not sure what concrete benefits it provides (if any at all?)
Sounds like a good idea to me. I was having some troubles then discovered that -SNAPSHOT
was what I needed to do anyway (not least because my library depended upon other -SNAPSHOT
libraries). And then I made another discovery: that with snapshots no signing is required. If in the future the signing barrier to entry is removed - then that will certainly save some time/frustration.
why is is that lein compile
doesn’t run the execution goal I have setup?
:plugins [[de.saumya.mojo/gem-maven-plugin "1.1.5"
:executions ([:execution
[:goals ([:goal "initialize"])]]
[:execution
[:goals ([:goal "exec"])]
[:phase "compile"]
[:configuration ([:execArgs "target/rubygems/bin/compass compile assets"])]])]]