stop using JCenter for publishing #469
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Main goal of this change is to phase out the use of JCenter before it is [sunset]. [sunset]: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ The following updates have been made: - Move from TravisCI to Github Actions. - Update to latest Nebula plugins. - Update to latest Gradle and codequality plugins. - Fix a few issues flagged by updated codequality plugins. - Remove API compatibility check. This broke for some and given the current state of Servo, it was just removed rather than trying to fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Main goal of this change is to phase out the use of
JCenter before it is sunset.
The following updates have been made:
and given the current state of Servo, it was just
removed rather than trying to fix.