[SPARK-52478] Use GCS Maven Central mirror as the primary repository
#246
Conversation
This file contains hidden or 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
Member
Author
|
Let me merge this since this is the same like Apache Spark. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR aims to use GCS
Maven Centralmirror as the primary repository.Why are the changes needed?
Since Apache Spark 3.0.0, Apache Spark community has been taking advantage of GCS
Maven Centralto stabilize and speed up CIs. We need to follow this practice in Apache Spark K8s Operator repository.In addition, this PR cleaned up the following which is a leftover of Apache Spark 4.0.0-SNAPSHOT usage before the official 4.0.0 release.
spark-kubernetes-operator/build.gradle
Lines 58 to 60 in 9705573
Does this PR introduce any user-facing change?
No behavior change. This is a build-only dev-side change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.