vs

Funnily enough, I now get

.... jitpack.io is a mistery

The only reference I've managed to find regarding upper/lowercase issues with Jitpack is this one: jitpack/jitpack.io#3722. And of course, even though GitHub is not case sensitive for names, Gradle definitely is, and according to that short thread, Jitpack also is.

So I'd rather just keep the "official" capitalization, but @rfc2822 may say otherwise.

A longer explanation:

I know about the issues there are building old releases, and honestly, I think it would be more suitable so use a Gradle host like Sonatype. When we moved from submodules to actual dependencies we used Jitpack just because it was simpler, not because it was better in any way. Also we didn't want to spend time on releases, just use commit ID, which Jitpack is great for.

Then, I know this works, but if we don't even know why, and the organization name is in capitals in GitHub, I would not like to change it now just "because for some reason it works better". We can try reopening jitpack/jitpack.io#3722 and see what they say.

It's an issue I run into occassionally and apparently other users as well (see the linked github issue I referenced).
If you want to try for yourself, checkout an older release and try to build it.
I honestly have no idea what the issues are on the jitpack.io side regarding case sensitive names, but certainly there are issues.

The all lower-case group-id names was the only "solution" I found so far. If you have a better solution, I'm all ears.

The only reference I've managed to find regarding upper/lowercase issues with Jitpack is this one: jitpack/jitpack.io#3722. And of course, even though GitHub is not case sensitive for names, Gradle definitely is, and according to that short thread, Jitpack also is.

That is not the only issue. See the issue I referenced jitpack/jitpack.io#3295 (comment) and it has many referenced issues.

thanks!