-
Notifications
You must be signed in to change notification settings - Fork 425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle build: switch from 'jcenter()' to 'mavenCentral()' [JCenter will not accept new artifacts after March 31st 2021] #1322
Comments
Wonderful, much appreciated! |
Hello @dejan2609, have you had a chance to look into this? If you can provide links to articles, that would also be useful. 👍 |
I have a few updates for you @remkop ! JFrog partially reversed their decision (they made one thing on Feb 3rd and then changed their mind on Feb 08th).
|
Some related links:
Now, I was quite busy investigating (going down the rabbit hole I found out many things: Note: related github issue link is intentionally posted like this (because it contains many related links from around the internet and requires about 20 minutes of reading |
To sum it up: it seems that you are free to release to JCenter now; herewith a new (changed) schedule:
But then again.... it is clear that many projects will seek for a new (permanent) place where they can publish (so, transition to a Maven Central is only a question of time). I hope I will be able to create some solution and push PR for your project in a few weeks (say, by the mid-March at the latest). Does that works for you ? |
@dejan2609 Sorry for my late reply. |
I may try to do a bugfix release this week in the next few days. |
I have a two news for you @remkop
This is a bad one: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter 😞
Good news is that I am here to help 😉
Complete solution will enable publishing to a Maven Central as easy as possible (and obviously all references to JCenter will be removed in favor of Maven Central).
Stay tuned, I will try to come up with something.
The text was updated successfully, but these errors were encountered: