[SPARK-45321][TESTS] Clean up the unnecessary Scala 2.12 related binary files #43106
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?
The purpose of this pr is to clean up the binary files used to assist with Scala 2.12 testing.
They include:
core/src/test/resources/TestHelloV3_2.12.jar
andcore/src/test/resources/TestHelloV2_2.12.jar
added by SPARK-44246([SPARK-44246][CONNECT][FOLLOW-UP] Miscellaneous cleanups for Spark Connect Jar/Classfile Isolation #41789).connector/connect/client/jvm/src/test/resources/udf2.12
andconnector/connect/client/jvm/src/test/resources/udf2.12.jar
added by SPARK-43744([SPARK-43744][CONNECT] Fix class loading problem caused by stub user classes not found on the server classpath #42069)connector/connect/client/jvm/src/test/resources/TestHelloV2_2.12.jar
added by SPARK-44293([SPARK-44293][CONNECT] Fix invalid URI for custom JARs in Spark Connect #41844)sql/hive/src/test/resources/regression-test-SPARK-8489/test-2.12.jar
added by SPARK-25304([SPARK-25304][SQL][TEST] Fix HiveSparkSubmitSuite SPARK-8489 test for Scala 2.12 #22308)Why are the changes needed?
Spark 4.0 no longer supports Scala 2.12.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No