-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-30572][BUILD] Add a fallback Maven repository #27281
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||
---|---|---|---|---|
|
@@ -257,6 +257,22 @@ | |||
<enabled>false</enabled> | ||||
</snapshots> | ||||
</repository> | ||||
<repository> | ||||
<id>central_without_mirror</id> | ||||
<!-- | ||||
This is used as a fallback when a mirror to `central` fail. | ||||
For example, when we use Google Maven Central in GitHub Action as a mirror of `central`, | ||||
this will be used when Google Maven Central is out of sync due to its late sync cycle. | ||||
--> | ||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, I mistakenly thought the maven automatically would do the fallback in the mirror failure case. How about leaving some comments, too, about this behaivour in the script of GitHub Actions? spark/.github/workflows/master.yml Line 69 in 19a1059
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure, @maropu . There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks! |
||||
<name>Maven Repository</name> | ||||
<url>https://repo.maven.apache.org/maven2</url> | ||||
<releases> | ||||
<enabled>true</enabled> | ||||
</releases> | ||||
<snapshots> | ||||
<enabled>false</enabled> | ||||
</snapshots> | ||||
</repository> | ||||
</repositories> | ||||
<pluginRepositories> | ||||
<pluginRepository> | ||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I get it. At this point though, would it just be easier to declare the Google repo above
central
above, and not use the mirror settings?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ur, I'm not sure that we can declare
Google Maven Central
as Apache Spark default repo because not everyone welcomeGoogle
repo. In Apache Spark, we only use this in GitHub Action. The other build environment, we don't useGoogle Maven Central
at all.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure, @srowen ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, it could be listed second. I don't see a problem with including a mirror as a repository here, as it's just a mirror of central. (We have had in the past, even, vendor-specific repos.) I hope it would have the same effect in improving robustness as anyone running the build would have it look at both repos before failing.