Migrate Publications to Maven Central
brianwernick opened this issue ยท 12 comments
- I have verified there are no duplicate active or recent bugs, questions, or requests
JFrog is ending support for JCenter by February 1st, 2022 in 2 parts:
- Stop accepting new publications on March 31st, 2021
- Shutdown servers on February 1st, 2022
This means that for ExoMedia to still be available after February 1st 2022 we need to migrate any existing versions to MavenCentral, and any new versions after March 31st 2021 will need to be published directly to MavenCentral.
That's nice to hear!
Hi there- if you have published to mavenCentral, please could you update your Readme to show the new implementation line we need to use
Thanks!
@KibiH No, this hasn't been published to Maven Central yet. Once we are ready for the 5.0 release we will publish to Maven Central and update all necessary documentation
any solution?
@brianwernick can you publish 5.0.0-snapshot version to mavenCentral, 4.3.0 version has dependencies conflict error, appcompat VS support.
ok.
repositories {
maven { url 'https://jitpack.io' }
}
dependencies {
implementation 'com.github.brianwernick:ExoMedia:master-SNAPSHOT'
}
@brianwernick please migrate this library from jcenter to mavenCentral. Because i can not run my application without this library. all of my project convert jcenter to mavencentral.
@brianwernick please migrate this library from jcenter to mavenCentral. Because i can not run my application without this library. all of my project convert jcenter to mavencentral.
I'm planning on tackling the migration work as part of the 5.0.0
release (I don't have a solid timeframe to communicate at this time), however in the meantime your app can still depend on JCenter as they have committed to continue hosting existing libraries for the foreseeable future (past the initial February 2022 date).
If you would like to limit the libraries that are pulled from JCenter you can do so by updating your repositories
definition in gradle to define the content, e.g.
jcenter() {
content {
// Included until ExoMedia is deployed to MavenCentral (https://github.com/brianwernick/ExoMedia/issues/723)
includeGroup "com.devbrackets.android"
}
}
Any update on this issue?
The deployment process has been updated so the next release will be published to Maven Central
Any update?