[SPARK-55710][BUILD] Use Google Mirror of Maven Central for SBT bootstrap#54508
[SPARK-55710][BUILD] Use Google Mirror of Maven Central for SBT bootstrap#54508yaooqinn wants to merge 1 commit intoapache:masterfrom
Conversation
…trap Change the default SBT bootstrap repository from Maven Central (repo1.maven.org) to Google's Maven Central mirror (maven-central.storage-download.googleapis.com) for downloading the sbt-launch jar. The rest of the SBT build already uses the Google mirror as the primary resolver (configured in project/repositories and project/SparkBuild.scala). This makes the bootstrap consistent and avoids flaky Maven Central connections. The DEFAULT_ARTIFACT_REPOSITORY environment variable can still override this. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
@yaooqinn This change itself looks good to me. Leave some comments. Is I think it's OK to do in a separate PR but should we change the following code as well? |
|
I revised the PR desc, thank you @sarutak |
This could be a user-facing change, I'm OK for it w/ a separate PR |
|
Thank you, @yaooqinn , @sarutak , @LuciferYang . |
What changes were proposed in this pull request?
Change the default SBT bootstrap repository from Maven Central (
repo1.maven.org) to Google's Maven Central mirror (maven-central.storage-download.googleapis.com) for downloading thesbt-launchjar.Why are the changes needed?
The rest of the SBT build already uses the Google mirror as the primary resolver, as
project/SparkBuild.scala. The bootstrap script (build/sbt-launch-lib.bash) was the only place still defaulting to Maven Central. This makes it consistent and avoids flaky Maven Central connections during the initialsbt-launchjar download.The
DEFAULT_ARTIFACT_REPOSITORYenvironment variable can still be used to override this.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manually tested by removing the cached
sbt-launch-1.12.4.jarand verifying the bootstrap successfully downloads from the Google mirror with matching checksum.Was this patch authored or co-authored using generative AI tooling?
Yes, GitHub Copilot CLI was used.