Migrate Gradle repo from jcenter to mavenCentral in dev projects #78812
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replace sunsetting
jcenter
withmavenCentral
, except fortrove4j
only indev
directory to work aroundcenter.bintray.com
flakiness in CI.This can be removed once
trove4j
is uploaded to Maven Central and we have a better migration story for Flutter apps, tracked with #78338More context at https://youtrack.jetbrains.com/issue/IDEA-261387 and #78338 (comment).
Fixes #78354