Adjust the maven source from repo.maven.apache.org to the apache CDN

[byjrack]

So repo.maven includes the maven bits, but also includes all the other Java packages along side it. That creates a bit of a challenge when we are trying to have folks use internal mirrors form policies. Basically the controls for java packages conflict with framework bootstraps like sdkman.

100% get that because the pointers are stored in the mongo db there is no easy way to support mirrors.

Instead of sourcing from the general purpose maven repo could the pointers be sent to the maven endpoints scoped specifically to the maven installer CDN? Gives me a path to have a conversation w the controls team to unlock a more tightly scoped endpoint

https://dlcdn.apache.org/maven/
https://archive.apache.org/dist/maven/

Archive for the archived/unsupported versions that the sdkman community might need to use.

Given I am not the "vendor" for maven it didn't seem like that was the appropriate path.

[marc0der]

Hey @byjrack,

We've had endless issues with the maven team dropping resources at a whim without telling anyone. For instance, the dlcdn will only work for a short time until the Maven team yanks them away and breaks all downstream dependents.

For this reason we've now standardised on the repo.maven URLs since they seem to offer more stability. Sorry that this might throw you, but it's the only way that we can guarantee stability to our consumers. That's until they decide to start tampering with those too! 😁

[byjrack]

Got it. I haven't noticed issues there, but my handful of requests won't compare to what your team sees every second.