-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
[Test Only][BUILD] Upgrade sbt
to 1.10.5
#48972
base: master
Are you sure you want to change the base?
Conversation
@@ -24,6 +24,9 @@ set -e | |||
FWDIR="$(cd "`dirname "$0"`"/..; pwd)" | |||
cd "$FWDIR" | |||
|
|||
# Skip maven local resolver. | |||
export SKIP_LOCAL_M2=true |
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.
We make dev/mima
ignore the maven local cache
directly, so that the environment and process that all tests depend on are consistent in both GA
and local
.
By using environment variables Based on this discussion coursier/coursier#2942 (comment), @LuciferYang @dongjoon-hyun Can we upgrade |
sbt
to 1.10.5
Resolver.file("ivyLocal", file(Path.userHome.absolutePath + "/.ivy2/local"))(Resolver.ivyStylePatterns) | ||
), | ||
DefaultMavenRepository) ++ | ||
{ if (sys.env.contains("SKIP_LOCAL_M2")) Nil else Seq(Resolver.mavenLocal) } :+ |
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.
Is there a way to exclude Resolver.mavenLocal
when it is explicitly known that the sbt task being executed is mimaReportBinaryIssues
What changes were proposed in this pull request?
The pr aims to upgrade sbt from
1.9.3
to1.10.5
.Why are the changes needed?
After version sbt
1.9.3
, if there are corrupt jars under the local (~/. m2), the GA's jobMIMA test
will fail to compile. Based on this, we added an environment variable (SKIP_LOCAL_M2
) inSparkBuild
to control whether to use theMaven Local Resolver
mechanism.Based on this discussion When there is a missing jar in Maven's local repo, it will fail. coursier/coursier#2942 (comment),
coursier
(sbt
relies on it) willnot
solve this problem in theshort
term.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.