sonatype.org is erring with 'too many requests' on CI about clutz HOT 8 CLOSED

It also doesn't sometimes work on my local machine. Sometimes it works though.

from clutz.

I don't know enough about Maven ecosystem, but maybe there is another mirror to use?

from clutz.

I don't know why we are not using Maven Central. @concavelenz do you have a suggestion for a better mirror?

from clutz.

It looks like closure-compiler-1.0-SNAPSHOT.jar is not in Maven Central, which is why we can't just us it.

from clutz.

I don't really understand it, but Sonatype is how we get our jars onto Maven. As far as I'm aware, everyone at Google uses it.

from clutz.

Here is a great resource here about the differences between Maven Central, JCenter, and sonatype.org.

TL;DR
Maven Central is the central place where all jars are stored. Next, JCenter is a newer superset of Maven Central, can have better download performance in some regions, and is the default repo used in Android projects and in build scripts made with gradle init.

https://oss.sonatype.org/content/repositories/snapshots is the location where releases are staged before they are released to Maven Central.

Since clutz is relying on the -SNAPSHOT version of closure compiler, we need to get it from https://oss.sonatype.org/content/repositories/snapshots. This is because -SNAPSHOT versions are special in Maven and specify the latest development version. On every build, when Maven resolves dependencies, it will always try the remote repository to get the latest -SNAPSHOT (as apposed to explicit versions that are cached).

Since clutz is relying directly on the development head of closure compiler, we need to use https://oss.sonatype.org/content/repositories/snapshots.

Long story short, we can't just use JCenter or Maven Central. Because of that I'm going to close this.

from clutz.

This keeps on failing, which means we have no recourse other than turning off tests :( Maybe it is time to switch to internal first development.

from clutz.

If you care to make 3p development work, I can solve this problem for you, just have JSCompiler and clutz in the same build. Using Bazel to solve this problem in open-source gives you the same-shaped solution as using Blaze to solve the problem in Piper.

from clutz.