custom domain quirk
Can you tell me why
https://jitpack.io/org/javacord/javacord-core/81d9e920/javacord-core-81d9e920.pom
is working fine, but
https://jitpack.io/org/javacord/javacord-core/c6d46c99/javacord-core-c6d46c99.pom
is returning Repo not found or no access token provided?
The commit-ish is valid in both cases, actually the second one is a parent of the merge commit that is the first one.
Actually I'd not even have expected the first one to work, as org.javacord is only pointing to the BtoBastian user, not to the Javacord repository.
https://jitpack.io/org/javacord/javacord/javacord-core/81d9e920/javacord-core-81d9e920.pom
and
https://jitpack.io/org/javacord/javacord/javacord-core/c6d46c99/javacord-core-c6d46c99.pom
both work as expected as now the repo is specified (domain org.javacord, repo Javacord, multi-project build artifact javacord-core).
But using org.javacord:javacord-core:c6d46c99 would be much preferable over org.javacord.javacord:javacord-core:c6d46c99, as the former is what will also be used for publication on MavenCentral.
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.