gocent | Go library to communicate with Centrifugo HTTP API | Websocket library

JetBrains copied org.jetbrains.trove4j:trove4j:20160824 to Maven Central, which resolves this error. 🎉

If you use additional dependencies that have not yet migrated to Maven Central, you should reach out directly to them.

Update: "We listened to the community and will keep JCenter as a read-only repository indefinitely. Our customers and the community can continue to rely on JCenter as a reliable mirror for Java packages." source

Update: Google is working on a fix for build tools 4.2 and maybe 4.1 as well. source

Update: You could try a dependency resolve rule.

The top-level dependency, com.android.tools.build:gradle, started using a newer version of trove4j in 7.0.0-alpha01. (7.0.0-alpha12 is currently the latest.)

Dependency chain: com.android.tools.build:gradle:7.0.0-alpha01 -> com.android.tools.build:builder:7.0.0-alpha01 -> com.android.tools:sdk-common:27.3.0-alpha01 -> org.jetbrains.intellij.deps:trove4j:1.0.20181211

However, this version is still in alpha and requires Android Studio 4.3+, which isn't even in Beta yet.

I have filed a bug with Google here: https://issuetracker.google.com/issues/179291081

Local/remote repositories aren't related to cloud v.s. on-prem. You deploy artifacts to local repositories (and then you can download them). You download artifacts from remote repositories, which proxy central artifacts servers such as bintray & maven-central. You will still be able to use bintray for your remote repositories until February 1st 2022, see blog for details. Since you're working on a clean setup I recommend using maven-central. You can find details of how to setup a remote gradle repository in the official documentation, including a video at the bottom.

I have solve this with multiple steps:

• First I have written a Java program to download all the artifacts from my JCenter account.
• Then I have write a Gradle script with the Maven plugin. This script use archiveBaseName, version and the directory of the artifacts as parameters. The script and maven plugin add all the missing things like the PGP signature.
• Then I write a Java program that iterate over the downloaded artifacts (or a part of it) and call the Gradle script with the parameters archiveBaseName, version and the directory with the artifacts in a loop.
• On the Sonatype GUI I deploy the uploaded files. Multiple version at once.

The follow code snippet which I have used will not work out of the box because it used internal private API. But it can help as start point. Of course you need an sonatype account and a gpg ring file. The secret properties are saved in the gradle.properties. You need also to customize the group name that the company used in all 3 files.

According to this and a note here of (both links to the official Microsoft Documentation) it seems to me, that at least your appcenter dependency should have been migrated to mavenCentral() by now. The time your question was asked and the time this issue has been raised lead me to believe that at the time you asked the question, this hasn't already been the case.

If you still have other dependencies that cannot be resolved, I'd advise you to research if the are still only availabel on JCenter.

The originating proxy should not matter and is not recorded: if you have downloaded the module from anywhere, then the bytes in your module cache should match the checksum found in either your go.sum file or the global checksum database.

(The go command fetches checksums for any new module dependencies from the database before downloading the module or adding the checksum to your go.sum file.)