-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-45046][BUILD] Set shadeTestJar of core module to false
#42766
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
Conversation
|
Set
All maven tests passed. |
|
cc @gengliangwang FYI |
|
@gengliangwang Do you still remember why changed |
I guess it was a mistake... |
|
BTW, there were multiple places setting |
|
@gengliangwang The |
|
@LuciferYang Got it, thanks! |
|
Merged into master. Thanks @gengliangwang @HyukjinKwon |
|
@gengliangwang After further investigation, there are three modules that depend on |

What changes were proposed in this pull request?
This pr aims to set
shadeTestJarofcoremodule tofalseto skip shadespark-core**-tests.jarprocess.Why are the changes needed?
Before SPARK-41244, the core module used the
maven-shade-pluginconfiguration in theparent pom.xmlfor shading, where theshadeTestJarconfiguration item was set to the defaultfalsein themaven-shade-plugininparent pom.xml.In SPARK-41244 | SPARK-41244 #38779, the core module started using a separate
maven-shade-pluginconfiguration and set theshadeTestJarconfiguration item totrue.And when
shadeTestJaris true,maven-shade-pluginalways try to find(sometime is downloading) some non-existent jars:Under poor network conditions, the time for Maven compilation will increase.
On the other hand, setting shadeTestJar back to false has not resulted in any Maven test failures, so this pr reset
shadeTestJartofalse.Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No