This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-31
Channels
- # announcements (22)
- # asami (19)
- # aws-lambda (4)
- # babashka (42)
- # beginners (43)
- # calva (28)
- # cider (1)
- # clerk (79)
- # clj-kondo (12)
- # clojure (47)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dev (12)
- # clojure-europe (40)
- # clojure-nl (2)
- # clojure-norway (5)
- # clojure-uk (3)
- # clojurescript (56)
- # clr (12)
- # conjure (8)
- # cursive (4)
- # datomic (78)
- # dev-tooling (6)
- # exercism (1)
- # fulcro (9)
- # hoplon (3)
- # jobs (3)
- # jobs-discuss (4)
- # lambdaisland (3)
- # leiningen (1)
- # london-clojurians (1)
- # lsp (125)
- # malli (32)
- # matcher-combinators (3)
- # nrepl (1)
- # off-topic (6)
- # pathom (39)
- # re-frame (13)
- # releases (2)
- # remote-jobs (3)
- # sci (7)
- # shadow-cljs (117)
- # sql (6)
- # squint (7)
- # tools-build (15)
- # tools-deps (12)
Isn't using two different libnames for tools.build (`io.github.clojure/tools.build` and org.clojure/tools.build
) https://github.com/clojure/tools.build#release-information an anti-pattern? If two libraries use two different lib names for the same library you might end up with the same library multiple times on the classpath and you wouldn't get the newest version of tools.build
I'm not aware of how io.github.clojure and org.clojure are resolved to the same thing
Sorry, I missed this thread earlier. You are correct, they are same nses under different coords
Unfortunately, not easy to reconcile
In Maven, we only have rights to that group. In git, if we change that one, you’ll need the url to resolve. I’ll think about it
@U064X3EF3 I guess one option would be to use org.clojure/tools.build
for the git dep as well
it is, but would not then get auto git/url resolution (and it conflicts with what we started with)
This is one reason I've not used the auto git/url resolution for projects I intended to publish to clojars
but it's one reason I haven't started adopting it for some projects. There was a time where people had both borkdude/sci
and org.babashka/sci
on their classpath and I used
to send PRs to migrate most of those
maven central does have a bunch of io.github projects (that's where we got this from originally), maybe I can just through the hoops to publish there
I've now authenticated io.github.clojure for our use as a groupId, working towards moving the maven artifact over there