This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-27
Channels
- # aleph (1)
- # announcements (5)
- # babashka (13)
- # beginners (68)
- # brompton (7)
- # calva (10)
- # cider (1)
- # clara (15)
- # cljsrn (2)
- # clojure (63)
- # clojure-austin (1)
- # clojure-europe (44)
- # clojure-france (2)
- # clojure-nl (5)
- # clojure-norway (1)
- # clojure-poland (1)
- # clojure-uk (8)
- # clojurescript (8)
- # clojureverse-ops (7)
- # conjure (13)
- # core-async (27)
- # cryogen (10)
- # cursive (17)
- # datomic (13)
- # deps-new (1)
- # events (1)
- # fulcro (3)
- # gratitude (4)
- # helix (6)
- # honeysql (6)
- # introduce-yourself (1)
- # jobs (2)
- # malli (13)
- # meander (9)
- # music (1)
- # news-and-articles (2)
- # off-topic (8)
- # pedestal (1)
- # reitit (4)
- # sci (25)
- # shadow-cljs (13)
- # spacemacs (2)
- # tools-build (5)
- # tools-deps (20)
- # vscode (50)
- # xtdb (2)
does deps-deploy work only with clojars? why would I use that instead of pemgranate ? I'm asking because I would like to publish to a private maven repo (Sonatype nexus) and don't know what to pick
I was checking out tools.build sources and I noticed the slf4j implementation there org.slf4j/slf4j-nop {:mvn/version "1.7.25"}
.
I believe that should not be set for a library in deps.
IMO the library should only depend on slf4j-api and use an implementation only in test aliases or similar.
My recommendation for such cases is to use org.slf4j/slf4j-simple {:mvn/version "1.7.25"}
:
:test {:extra-paths ["src/test/clojure"]
:extra-deps {io.github.cognitect-labs/test-runner
{:git/url ""
:sha "705ad25bbf0228b1c38d0244a36001c2987d7337"}
org.slf4j/slf4j-simple {:mvn/version "1.7.25"}}
In this case tools.build is designed to be used as an application and generally I don’t find the logging to be of much use
If it was not included here, every user of tools.build would have to include a log impl
Yeah, I think it's reasonable to require someone to exclude the log impl if they want a different one.