I created an issue to track the conversation around relocating lambdaisland artifacts to com.lambdaisland. My thinking has shifted a bit on this, and we're going to hold off on deploying existing libraries to com.lambdaisland until Clojars and tools.deps have figured out relocation support (which, realistically, may be never, unless we make it happen). https://github.com/lambdaisland/open-source/issues/2

@plexus May I ask what is the reason for this relocation? Clojars only requires this for new groupnames right?

Consistency.

Keep our tooling consistent, and don't add another thing we and our users need to keep track of.

As explained in the issue > For existing libraries we could keep using lambdaisland/..., but that would mean keeping track of which ones are "new world" vs "old world" across over a dozen libraries

But why not push the new libraries to the old group name as well?

we can't, it's not allowed

😨

Ah right… I guess the clojars grandfathering is for existing libs only, right? So when you have a new lambdaisland lib you want to push you are out of luck!