This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-07
Channels
- # adventofcode (202)
- # aleph (8)
- # announcements (13)
- # architecture (1)
- # aws (2)
- # beginners (201)
- # boot (1)
- # bristol-clojurians (1)
- # calva (2)
- # cider (23)
- # cljs-dev (22)
- # cljsrn (2)
- # clojure (105)
- # clojure-bangladesh (1)
- # clojure-berlin (8)
- # clojure-dev (104)
- # clojure-europe (3)
- # clojure-italy (5)
- # clojure-losangeles (1)
- # clojure-nl (24)
- # clojure-russia (55)
- # clojure-spec (44)
- # clojure-uk (19)
- # clojurescript (58)
- # component (58)
- # cursive (3)
- # data-science (1)
- # datomic (27)
- # duct (6)
- # events (6)
- # figwheel-main (6)
- # fulcro (15)
- # jobs (3)
- # kaocha (5)
- # luminus (1)
- # music (1)
- # nrepl (2)
- # off-topic (24)
- # onyx (1)
- # pedestal (3)
- # protorepl (8)
- # re-frame (18)
- # reagent (39)
- # reitit (1)
- # remote-jobs (1)
- # ring (15)
- # rum (11)
- # shadow-cljs (5)
- # sql (8)
- # tools-deps (12)
- # vim (7)
What tools do folk like to use to build and publish jar artifacts to maven repos, particularly private s3 maven repos?
At work we use https://github.com/seancorfield/depstar to build our deployment uberjars and I also use it now to build "thin" JARs to deploy on Clojars.
For the actual "push", I use mvn deploy:deploy-file ...
(the same, nasty invocation that @U09LZR36F has in his blog post, wrapped up in a shell script -- that also updates pom.xml
with the SHA of the latest commit so that Clojars can link back to the commit that created the release)
Thanks for the pointers!
FWIW, I'm working on a tool to post-process the results of clojure -Spom
to add in the groupId/artifactId and pull the version from a git tag, since checking in partly-generated stuff into source control bugs me
(with the goal of automating everything up to the jar creation and then using pack for the rest)
If I create a pom.xml
with the following dependency:
<dependency>
<groupId>org.lmdbjava</groupId>
<artifactId>lmdbjava</artifactId>
<version>0.6.1</version>
</dependency>
and run mvn dependency:tree
I see lmdbjava
with 10 transitive dependencies. If I create a deps.edn
with the same dependency:
{:deps {org.lmdbjava/lmdbjava {:mvn/version "0.6.1"}}}
and run clj -Stree
I see 9 transitive dependencies. com.github.jnr:jffi:jar:native:1.2.16:runtime
is missing. Could this be an issue with tools.deps
?Sounds like https://dev.clojure.org/jira/browse/TDEPS-50 maybe?