Haven't looked but... do they normalize to the same library group/artifact internally?

Technically I think they might be considered duplicate keys, ya?

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

no that's incorrect, clojars also supports io.github.borkdude

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

I'm risking sounding a bit like I'm wearing a tin foil hat but I personally would try and avoid coupling my artifact names to a giant corporation I don't have control over