-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Migrate artifacts to a different repository #606
Comments
Thanks for the notice, will find a new repository soon. |
This may also help. |
Thanks for that link. Will get the next releases into Sonatype OSSRH and Maven Central. Not sure whether it's feasible to also migrate all the old releases over, since at minimum we'd need additional metadata. Perhaps a couple of the most actively-used releases. |
That's great news! I don't know if it is the same for others, but I would specifically need version 3.3.0 ( |
Likewise. |
Another nice helping article: Migrating old artifacts from JCenter to MavenCentral This helps you manually migrate desired versions easily |
Any updates? |
It seems like JCenter will keep the artifacts 1 extra year. - No hurry so far |
Released v4.2.0 using new config in #617. Also manually migrated versions 3.3.0, 3.5.0, 3.6.0 and 4.1.0. |
Description of the problem:
Jfrog is going to deprecate and disable jcenter services - artifact migration will be needed
https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
The text was updated successfully, but these errors were encountered: