This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-07
Channels
- # adventofcode (4)
- # aleph (1)
- # architecture (9)
- # beginners (67)
- # boot (7)
- # boot-dev (12)
- # cider (3)
- # clojure (166)
- # clojure-austin (3)
- # clojure-estonia (1)
- # clojure-greece (2)
- # clojure-russia (5)
- # clojure-spec (1)
- # clojure-uk (4)
- # clojurescript (19)
- # cursive (1)
- # data-science (5)
- # datascript (4)
- # datomic (3)
- # docs (10)
- # emacs (24)
- # events (4)
- # fulcro (16)
- # graphql (8)
- # hoplon (2)
- # jobs-discuss (1)
- # leiningen (5)
- # off-topic (2)
- # planck (30)
- # re-frame (20)
- # reagent (36)
- # ring (3)
- # shadow-cljs (5)
- # spacemacs (1)
- # specter (2)
im not really sure, i guess you could make an issue on the clojars-web repo requesting it or something
@rymndhng I don't think you should be able to trigger it as shadowing isn't allowed for new deploys unless you're whitelisted
I wrote a guide on public maven repositories that you're likely to encounter on the JVM: https://www.deps.co/guides/public-maven-repositories/
@rymndhng The shadow warning is only for artifacts that were deployed to both maven central and clojars, which clojars used to allow but does no longer. Things that are whitelisted can still be deployed to clojars even if they are on central, but won't have the shadow warning (which is currently only https://clojars.org/net.mikera/clojure-pom, because it was deployed to central originally, then moved to clojars)